Triple
T1984746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Louis Lambert International Airport |
E43114
|
entity |
| Predicate | hasAirportDiagram |
P35786
|
FINISHED |
| Object | published by FAA |
—
|
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: published by FAA | Statement: [St. Louis Lambert International Airport, hasAirportDiagram, published by FAA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAirportDiagram Context triple: [St. Louis Lambert International Airport, hasAirportDiagram, published by FAA]
-
A.
isPartOfAirportLayout
Indicates that something is a component or element within the overall physical or functional layout of an airport.
-
B.
hubAirport
Indicates that an airport serves as a primary hub or central operating base for a particular airline or carrier.
-
C.
hasAirportWithinJurisdiction
Indicates that a governing authority or administrative region has legal or administrative control over an airport located within its boundaries.
-
D.
isCivilAirport
Indicates that an airport is designated and used primarily for civilian (non-military) aviation operations.
-
E.
hasStationAtAirport
Indicates that an organization or service operates a station or facility located at a specific airport.
- F. None of above. chosen
Provenance (4 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_69a88713ddc88190a969715658ebe7a8 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb96f932881908bebfc4176fda7c0 |
completed | March 7, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69abb798d288819083132cf14605bd02 |
completed | March 7, 2026, 5:28 a.m. |
| PDg | Predicate description generation | batch_69abb96e07c08190beed60096e9d71b4 |
completed | March 7, 2026, 5:36 a.m. |
Created at: March 4, 2026, 7:37 p.m.