Triple
T36094426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SLU Airport |
E1044017
|
entity |
| Predicate | servesDomesticTrafficWithinCountry |
P201897
|
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: [SLU Airport, servesDomesticTrafficWithinCountry, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesDomesticTrafficWithinCountry Context triple: [SLU Airport, servesDomesticTrafficWithinCountry, yes]
-
A.
servesDomesticNetwork
chosen
Indicates that an entity provides service or coverage within a country’s internal or domestic network.
-
B.
servedDomesticDestination
Indicates that a transportation service (such as an airline or train operator) provided service to a destination located within the same country.
-
C.
isDomesticRouteIn
Indicates that a transportation route operates entirely within the boundaries of a specified country or internal region.
-
D.
facilitatesTravelWithin
Indicates that one entity enables or makes it easier for another entity to move or travel within a specific area or region.
-
E.
hasPassengerTrafficFrom
Indicates that an entity receives or handles passenger traffic originating from another entity.
- 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_69f76e32d60c8190ba781ffaaab4aa3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a00332eaa0c8190a69ea895576bb0ee |
completed | May 10, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_6a0032b2ea80819083b89ebb88165933 |
completed | May 10, 2026, 7:24 a.m. |
Created at: May 3, 2026, 4:08 p.m.