Triple
T37177752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gustavo Rojas Pinilla International Airport |
E921101
|
entity |
| Predicate | airTrafficType |
P91661
|
FINISHED |
| Object | civil |
—
|
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: civil | Statement: [Gustavo Rojas Pinilla International Airport, airTrafficType, civil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airTrafficType Context triple: [Gustavo Rojas Pinilla International Airport, airTrafficType, civil]
-
A.
airTraffic
Indicates the movement and flow of aircraft through airspace, including their routes, density, and interactions while in flight.
-
B.
airspaceType
Indicates the classification or category of airspace that applies to a given location or flight segment.
-
C.
typeOfAviation
chosen
Indicates the specific category or kind of aviation to which an entity belongs (e.g., commercial, military, private).
-
D.
airTrafficRole
Indicates the specific function or responsibility an entity has within the context of air traffic operations or control.
-
E.
airTransportType
Indicates the specific mode or category of transportation by air associated with an entity or event.
- 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_69f76ea16f288190b445aa1604d996f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.