Triple
T29774249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AJL |
E755332
|
entity |
| Predicate | associatedAirportElevationCategory |
P128627
|
FINISHED |
| Object | elevated terrain airport |
—
|
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: elevated terrain airport | Statement: [AJL, associatedAirportElevationCategory, elevated terrain airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedAirportElevationCategory Context triple: [AJL, associatedAirportElevationCategory, elevated terrain airport]
-
A.
airportElevationMetres
Indicates the vertical height of an airport above mean sea level, measured in metres.
-
B.
airportElevationFeet
Indicates the elevation of an airport above sea level, measured in feet.
-
C.
boardingElevation
Indicates the elevation at which boarding occurs for a vehicle or transport facility, typically relative to a standard reference level.
-
D.
approximateElevationCategory
chosen
Indicates the general elevation range or level into which an entity’s height above sea level has been coarsely grouped.
-
E.
airportElevationUnit
Indicates the unit of measurement used to express the elevation of an airport.
- 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_69f0ef878574819088c867fd1a5c8b86 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 28, 2026, 8:45 p.m.