Triple
T31547464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philadelphia Zoning Board of Adjustment |
E804907
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | quasi-judicial board |
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 board Context triple: [Philadelphia Zoning Board of Adjustment, instanceOf, quasi-judicial board]
-
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.
judicial commission
A judicial commission is an official body, often temporary and independent, established to investigate, review, or make recommendations on specific legal or public-interest matters.
-
D.
administrative tribunal
An administrative tribunal is a specialized quasi-judicial body that resolves disputes and makes determinations arising from the decisions or actions of government agencies under specific statutory frameworks.
-
E.
judicial panel
A judicial panel is a group of judges convened together to hear, deliberate on, and decide a legal case or set of related legal issues.
- 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_69f348d11a048190a65eb8384a3754ac |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:09 p.m.