Triple
T11551086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Bend Airport station |
E273890
|
entity |
| Predicate | openedAsAirportTerminus |
P70253
|
FINISHED |
| Object | 1992 |
—
|
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: 1992 | Statement: [South Bend Airport station, openedAsAirportTerminus, 1992]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsAirportTerminus Context triple: [South Bend Airport station, openedAsAirportTerminus, 1992]
-
A.
openedAsTransitStation
Indicates that an entity began operation specifically as a transit station at the time it was opened.
-
B.
openedAsCivilAirport
Indicates that a facility or location began operation specifically as a civil (non-military) airport.
-
C.
openedAsMainAirport
Indicates that an airport was inaugurated or began operation specifically in the role of the primary or principal airport for a given city or region.
-
D.
openedAsTerminus
chosen
Indicates that a transportation line or route was initially opened with this location serving as its end-point terminus.
-
E.
newPassengerTerminalOpened
Indicates that a new passenger terminal has begun operations and is now open for use.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88a83f1e88190aabf11a4c8a6c9e5 |
completed | April 10, 2026, 5:28 a.m. |
| PD | Predicate disambiguation | batch_69d8087e57b48190a4c253dc0210f9d4 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.