Triple
T10517359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Class B airspace |
E248068
|
entity |
| Predicate | hasUpperLimit |
P36360
|
FINISHED |
| Object | typically 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: typically 10,000 feet MSL | Statement: [Class B airspace, hasUpperLimit, typically 10,000 feet MSL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUpperLimit Context triple: [Class B airspace, hasUpperLimit, typically 10,000 feet MSL]
-
A.
upperLimit
chosen
Indicates that one entity specifies the maximum allowable value, quantity, or boundary for another entity or condition.
-
B.
hasMaximumValue
Indicates that one value in a set is the greatest or highest possible according to a specified criterion.
-
C.
isLimitOf
Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
-
D.
hasLimitation
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
E.
canBeExceededIn
Indicates that one entity’s value, level, or extent is capable of being surpassed by that of another entity within a specified context.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509cd0fb8819087de2f9a93bad6e6 |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb94fa10819091f585bab4379c6f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:28 p.m.