Triple
T20394795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nantes Atlantique Airport |
E500172
|
entity |
| Predicate | hasCode |
P9567
|
FINISHED |
| Object | NTE |
—
|
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: NTE | Statement: [Nantes Atlantique Airport, hasCode, NTE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: NTE Context triple: [Nantes Atlantique Airport, hasCode, NTE]
-
A.
NTE
chosen
NTE is the IATA airport code for Nantes Atlantique Airport, the main international airport serving the city of Nantes in western France.
-
B.
NGTE
NGTE is the ICAO airport code for Tabiteuea Airport, a regional airfield serving Tabiteuea in Kiribati.
-
C.
NTTA
NTTA is the regional agency responsible for planning, building, operating, and maintaining toll roads and related transportation infrastructure in the North Texas area.
-
D.
EETN
EETN is the ICAO airport code for Lennart Meri Tallinn Airport, the main international airport serving Tallinn, Estonia.
-
E.
NT1
NT1 is the former name of TFX, a company that has since rebranded under its current title.
- 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_69e0b4a71ebc8190b153a36c738730f4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e679122058819083e3615a5ea0a82e |
completed | April 20, 2026, 7:05 p.m. |
Created at: April 16, 2026, 11:28 a.m.