Triple
T12797138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cook County townships |
E305917
|
entity |
| Predicate | typicalOffices |
P5164
|
FINISHED |
| Object | township supervisor |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: township supervisor | Statement: [Cook County townships, typicalOffices, township supervisor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalOffices Context triple: [Cook County townships, typicalOffices, township supervisor]
-
A.
officeIn
Indicates that one entity has an office located within the premises or jurisdiction of another entity.
-
B.
officeUnder
Indicates that one office is subordinate to, managed by, or organizationally within the authority of another office.
-
C.
hasOfficeType
chosen
Indicates that an entity’s office is classified as a specific type or category of office.
-
D.
controlledOffice
Indicates that one entity has authority over, manages, or directs the operations of a particular office or administrative location.
-
E.
comparableOffice
Indicates that two offices are sufficiently similar in relevant characteristics (such as size, function, or status) to be meaningfully compared to each other.
- F. None of above.
Provenance (3 batches)
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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e6db68481909a2ca8da1287f3e0 |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ed7448190b276e7fab649f7d2 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:30 p.m.