Triple
T265682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Committee on Zoning, Landmarks and Building Standards |
E5720
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | municipal legislative committee |
C124
|
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 legislative committee Context triple: [Committee on Zoning, Landmarks and Building Standards, instanceOf, municipal legislative committee]
-
A.
municipality
A municipality is a local administrative unit, such as a city, town, or district, governed by elected officials and responsible for providing public services and regulations within its defined geographic area.
-
B.
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.
-
C.
subnational legislature
A subnational legislature is a lawmaking body that operates below the national level—such as a state, provincial, or regional assembly—responsible for creating and overseeing laws and policies within its specific territorial jurisdiction.
-
D.
legislative body
chosen
A legislative body is an organized group of elected or appointed representatives empowered to create, amend, and repeal laws and oversee government policy within a political system.
-
E.
governing council
A governing council is a formal body of appointed or elected individuals responsible for making high-level decisions, setting policies, and providing oversight for an organization, community, or institution.
- 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_69a2587daeb081909591b9d30f80a271 |
completed | Feb. 28, 2026, 2:52 a.m. |
Created at: Feb. 28, 2026, 2:56 a.m.