Triple
T12965926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raleigh Historic Development Commission |
E321262
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | municipal advisory board |
C5960
|
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: municipal advisory board Context triple: [Raleigh Historic Development Commission, instanceOf, municipal advisory board]
-
A.
municipal advisory committee
chosen
A municipal advisory committee is a formally appointed group of community members that provides recommendations and expert input to local government officials on specific policy areas, projects, or issues.
-
B.
municipal board
A municipal board is a local governing body composed of appointed or elected members responsible for making decisions, setting policies, and overseeing specific functions or services within a municipality.
-
C.
municipal government committee
A municipal government committee is a formally organized group within a local government tasked with studying specific issues, advising the city or town council, and sometimes making decisions or recommendations on policies, services, and regulations affecting the community.
-
D.
municipal organization
A municipal organization is a local government entity responsible for providing public services, managing community resources, and implementing policies within a city, town, or other local jurisdiction.
-
E.
municipal agency
A municipal agency is a local government organization responsible for delivering specific public services, enforcing local regulations, and managing community programs within a city or town.
- 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_69d80763bd6c819094437da5b20b01d2 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 8:28 p.m.