Triple
T191963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regional Transportation Authority of Northeastern Illinois |
E3739
|
entity |
| Predicate | hasBoardOfDirectors |
P2886
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Regional Transportation Authority of Northeastern Illinois, hasBoardOfDirectors, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBoardOfDirectors Context triple: [Regional Transportation Authority of Northeastern Illinois, hasBoardOfDirectors, yes]
-
A.
numberOfBoardMembers
Indicates the total count of individuals who serve as members on a board.
-
B.
hasCommittee
Indicates that an entity is associated with or overseen by a specific committee.
-
C.
executiveBody
Indicates that an entity serves as the executive governing authority or decision-making body for another entity.
-
D.
hasMainGoverningBody
chosen
Indicates that an entity possesses a primary official organization or authority responsible for its overall governance or decision-making.
-
E.
hasOrganizationalStructure
Indicates that an entity possesses a defined internal arrangement of roles, responsibilities, and relationships that determine how it is organized and operates.
- 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_69a2548debd48190ae3a06d6e65b53c6 |
completed | Feb. 28, 2026, 2:35 a.m. |
| NER | Named-entity recognition | batch_69a259669ba08190a5be1d2e10e70b27 |
completed | Feb. 28, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69a2567567508190b3a41329a15c7156 |
completed | Feb. 28, 2026, 2:44 a.m. |
Created at: Feb. 28, 2026, 2:41 a.m.