Triple
T22694006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Carolina State Historic Records Advisory Board |
E561122
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state historical records advisory board |
C3980
|
CONCEPT FINISHED |
How this triple was built (1 step)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: state historical records advisory board Context triple: [North Carolina State Historic Records Advisory Board, instanceOf, state historical records advisory board]
-
A.
historic preservation commission
A historic preservation commission is a governing body that identifies, protects, and regulates historically significant buildings, sites, and districts within a community.
-
B.
heritage committee
A heritage committee is a group of appointed or elected individuals responsible for identifying, preserving, and advising on the protection and promotion of cultural, historical, or natural heritage resources within a community or organization.
-
C.
state government commission
chosen
A state government commission is an officially authorized body established by a state to investigate, regulate, advise on, or administer specific public policy areas or functions within its jurisdiction.
-
D.
historical policy
Historical policy is a conceptual class encompassing formal rules, laws, and governance decisions implemented in the past that shaped societal, economic, and political developments over time.
-
E.
state transportation board
A state transportation board is a governing body that oversees planning, funding, and policy decisions for a state’s transportation systems and infrastructure.
- F. None of above.
Provenance (1 batch)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e2454e615481909c177440be559d2c |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 3:14 p.m.