Triple
T23892589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meigs Field |
E600811
|
entity |
| Predicate | hadTerminalBuilding |
P36334
|
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: [Meigs Field, hadTerminalBuilding, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadTerminalBuilding Context triple: [Meigs Field, hadTerminalBuilding, yes]
-
A.
hasTerminalBuildings
chosen
Indicates that one entity possesses or includes terminal buildings associated with it.
-
B.
hasSmallTerminalBuilding
Indicates that an entity possesses a terminal building that is relatively small in size or capacity.
-
C.
terminalBuildingCompleted
Indicates that the construction of a terminal building has been finished and it is considered complete.
-
D.
hasFormerBuilding
Indicates that an entity previously occupied or used a different building, which is identified as its former building.
-
E.
hasTerminalFacility
Indicates that an entity possesses or includes a terminal facility used as an endpoint for transport, communication, or related operations.
- 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_69e295341ac0819080647f2908af793c |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cd044708819091102ecc160e1961 |
completed | April 29, 2026, 9:19 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:25 p.m.