Triple
T23050613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mariscal Lamar International Airport |
E573999
|
entity |
| Predicate | isHighAltitudeAirport |
P73807
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Mariscal Lamar International Airport, isHighAltitudeAirport, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHighAltitudeAirport Context triple: [Mariscal Lamar International Airport, isHighAltitudeAirport, yes]
-
A.
isHighElevation
chosen
Indicates that an entity is located at or associated with a relatively high altitude or elevation above a reference level, typically sea level.
-
B.
meetsAtAltitude
Indicates that two or more entities come together or intersect at a specific vertical height or elevation.
-
C.
locatedAtAltitude
Indicates that an entity exists or is positioned at a specific height above a reference level, typically sea level.
-
D.
altitudeCapability
Indicates the maximum or typical altitude at which an entity can effectively operate or function.
-
E.
hasAltitudeFeature
Indicates that an entity possesses a characteristic or attribute related to its elevation or vertical position above a reference level.
- 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_69e245b9c11481909d06c872214d21af |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1867c443081909588262bc90748af |
completed | April 29, 2026, 4:18 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
Created at: April 17, 2026, 3:54 p.m.