Triple
T2247984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Class B airspace |
E49550
|
entity |
| Predicate | hasTypicalUpperLimit |
P14327
|
FINISHED |
| Object | 10,000 feet MSL |
—
|
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: 10,000 feet MSL | Statement: [Class B airspace, hasTypicalUpperLimit, 10,000 feet MSL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalUpperLimit Context triple: [Class B airspace, hasTypicalUpperLimit, 10,000 feet MSL]
-
A.
isLimitOf
Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
-
B.
hasMaximumValue
Indicates that one value in a set is the greatest or highest possible according to a specified criterion.
-
C.
hasLimitation
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
D.
isUpperBoundFor
chosen
Indicates that one value is greater than or equal to every element in a given set or collection, serving as an upper limit for them.
-
E.
hasUpperBarLength
Indicates that an entity possesses an upper bar whose length is specified or constrained by the related value or object.
- 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_69a88aa979788190ad6500f1d8eee2fc |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc0ed5c38819080b45ea398fb59f2 |
completed | March 7, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69abbdb160248190aa75b38f11ad8602 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.