Triple
T14304221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 13L/31R |
E354648
|
entity |
| Predicate | icaoAirportCode |
P419
|
FINISHED |
| Object | SKBO |
E52197
|
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: SKBO | Statement: [Runway 13L/31R, icaoAirportCode, SKBO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SKBO Context triple: [Runway 13L/31R, icaoAirportCode, SKBO]
-
A.
SKBO
chosen
SKBO is the ICAO airport code for El Dorado International Airport, the main international gateway serving Bogotá, Colombia.
-
B.
SKO
SKO is the abbreviation for the Saito Kinen Orchestra, a renowned Japanese classical ensemble founded by conductor Seiji Ozawa in honor of his teacher Hideo Saito.
-
C.
SK
SK is the vehicle registration code used on license plates for vehicles registered in Skopje, the capital city of North Macedonia.
-
D.
SK
SK is the archaeological site code for Swartkrans, a significant South African paleoanthropological cave site known for its early hominin fossils and stone tools.
-
E.
SK
SK is the vehicle registration code for the district of Saalekreis in the German state of Saxony-Anhalt.
- 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_69d8278e17088190b328c5a9d4be74ff |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de85afabe48190926d6098047f4bcf |
completed | April 14, 2026, 6:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd3d2a56a4819095b5c2164b1ad9fb |
completed | May 8, 2026, 1:32 a.m. |
Created at: April 10, 2026, 1:12 a.m.