Triple
T23498556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corumbá International Airport |
E571770
|
entity |
| Predicate | usesRunwayNumber |
P8866
|
FINISHED |
| Object | 18/36 |
—
|
LITERAL 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: 18/36 | Statement: [Corumbá International Airport, usesRunwayNumber, 18/36]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRunwayNumber Context triple: [Corumbá International Airport, usesRunwayNumber, 18/36]
-
A.
usesRunwayNumberingConvention
Indicates that an airport or runway follows a specific standardized system for assigning runway identification numbers.
-
B.
hasRunwayNumber
chosen
Indicates that an airport or airfield runway is assigned a specific identifying number.
-
C.
usesRunwayOf
Indicates that one entity makes use of the runway that belongs to or is associated with another entity.
-
D.
isRunwayOf
Indicates that a physical runway is a component or facility belonging to, used by, or officially associated with a particular airport or airfield.
-
E.
usesRunwayAlternation
Indicates that runway usage is alternated between different runways or runway directions according to a defined pattern or schedule.
- 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_69e245b4829881909b77a70e942bbd54 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7e184ec8190aff3677c9b00a8f2 |
completed | April 29, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:06 p.m.