Triple
T2229346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Class A airspace |
E48727
|
entity |
| Predicate | altimeterSettingReference |
P36365
|
FINISHED |
| Object | standard pressure setting 29.92 inHg |
—
|
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: standard pressure setting 29.92 inHg | Statement: [Class A airspace, altimeterSettingReference, standard pressure setting 29.92 inHg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: altimeterSettingReference Context triple: [Class A airspace, altimeterSettingReference, standard pressure setting 29.92 inHg]
-
A.
airportElevationFeet
Indicates the elevation of an airport above sea level, measured in feet.
-
B.
locatedAtAltitude
Indicates that an entity exists or is positioned at a specific height above a reference level, typically sea level.
-
C.
hasAtmosphericPressureAtSeaLevel
Indicates that an entity possesses a specific value of atmospheric pressure measured at sea level.
-
D.
altitudeOfRecordFlight
Indicates the altitude reached during a particular record-setting flight.
-
E.
altitudeProfile
Indicates the variation of elevation or height along a path, route, or trajectory over distance or time.
- F. None of above. chosen
Provenance (4 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_69a88aa51b388190949868ec9766e587 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc0685b688190857a76c1043f4b92 |
completed | March 7, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69abbdadbb0c8190b3a1ede31b8acbfa |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbe4252688190944491a450383450 |
completed | March 7, 2026, 5:57 a.m. |
Created at: March 4, 2026, 7:47 p.m.