Triple
T7028719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 06/24 |
E163215
|
entity |
| Predicate | icaoAirportCode |
P419
|
FINISHED |
| Object | LTFJ |
E161449
|
NE 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: LTFJ | Statement: [Runway 06/24, icaoAirportCode, LTFJ]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LTFJ Context triple: [Runway 06/24, icaoAirportCode, LTFJ]
-
A.
LTFJ
chosen
LTFJ is the ICAO airport code for Istanbul Sabiha Gökçen International Airport, a major international airport serving the Asian side of Istanbul, Turkey.
-
B.
LFTW
LFTW is the ICAO airport code for Nîmes-Alès-Camargue-Cévennes Airport in southern France.
-
C.
TLF
TLF is the abbreviation commonly used for the Turkish Land Forces, the main ground warfare branch of Turkey’s military.
-
D.
LTFM
LTFM is the ICAO airport code for Istanbul Airport, the main international airport serving Istanbul, Turkey.
-
E.
FJT
FJT is the standard time zone used in Fiji, typically 12 hours ahead of Coordinated Universal Time (UTC+12) and sometimes observing daylight saving time.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c6885d691c81908cf7d31083113886 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e200ecdc819098ca07473dfb272a |
completed | March 27, 2026, 8:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7758c87908190bd1ddcfdccc171b5 |
completed | March 28, 2026, 6:30 a.m. |
Created at: March 27, 2026, 2:35 p.m.