Triple
T35840646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LAX air traffic control tower |
E1036067
|
entity |
| Predicate | icaoAirportCodeServed |
P119919
|
FINISHED |
| Object | KLAX |
—
|
NE NERFINISHED |
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: KLAX | Statement: [LAX air traffic control tower, icaoAirportCodeServed, KLAX]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: icaoAirportCodeServed Context triple: [LAX air traffic control tower, icaoAirportCodeServed, KLAX]
-
A.
airportServed
Indicates that a particular airport provides service to, or is used for air travel to and from, a given location or area.
-
B.
servesAirportICAO
chosen
Indicates that a transportation service or facility operates routes to or from the airport identified by the given ICAO code.
-
C.
airportIATAAssociated
Indicates that an airport is associated with a specific IATA (International Air Transport Association) code.
-
D.
airportCodeFAA
Indicates that an airport is identified by a specific FAA (Federal Aviation Administration) airport code.
-
E.
airportIdentifier
Indicates that an entity is identified by a specific airport code or designation within an aviation identification system.
- 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_69f76e1a29e8819088280f26096aeb55 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.