Triple
T35639511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quincy Zoning Board of Appeals |
E1029818
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | quasi-judicial municipal body |
C2308
|
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: quasi-judicial municipal body Context triple: [Quincy Zoning Board of Appeals, instanceOf, quasi-judicial municipal body]
-
A.
quasi‑judicial body
chosen
A quasi-judicial body is an administrative or regulatory entity that has powers and procedures resembling those of a court, enabling it to interpret laws, conduct hearings, and make binding decisions or recommendations in specific areas of public or private disputes.
-
B.
quasi-judicial officer
A quasi-judicial officer is an individual or body authorized by law to conduct hearings, evaluate evidence, and make determinations or recommendations that resemble judicial decisions, but within an administrative or specialized regulatory context rather than a traditional court.
-
C.
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.
-
D.
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.
-
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_69f76e087bdc8190a4794bf9c0bd7634 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.