Triple
T17852106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 08R/26L |
E445832
|
entity |
| Predicate | airportIATA |
P418
|
FINISHED |
| Object | TXL |
—
|
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: TXL | Statement: [Runway 08R/26L, airportIATA, TXL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TXL Context triple: [Runway 08R/26L, airportIATA, TXL]
-
A.
TXL
chosen
TXL was the IATA airport code for Berlin Tegel Airport, the former main international airport of Berlin, Germany.
-
B.
TXP
TXP is the station code used to identify Tianjin West Railway Station in China’s railway network.
-
C.
TXK
TXK is the IATA airport code for Texarkana Regional Airport, which serves the Texarkana area in Texas and Arkansas.
-
D.
TZX
TZX is the IATA airport code for Trabzon Airport, a regional airport serving the city of Trabzon on Turkey’s Black Sea coast.
-
E.
TXN
TXN is the stock ticker symbol for Texas Instruments Incorporated, a major American technology company known for designing and manufacturing semiconductors and integrated circuits.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9f26f18819089c9e43250bee6ae |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48fff6c288190a2b5e60b66c03ddc |
completed | April 19, 2026, 8:19 a.m. |
Created at: April 10, 2026, 10:17 a.m.