Triple
T26281611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulfstream G800 |
E660712
|
entity |
| Predicate | cabinAltitude_ft |
P90924
|
FINISHED |
| Object | 2900 at 41000 ft |
—
|
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: 2900 at 41000 ft | Statement: [Gulfstream G800, cabinAltitude_ft, 2900 at 41000 ft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cabinAltitude_ft Context triple: [Gulfstream G800, cabinAltitude_ft, 2900 at 41000 ft]
-
A.
cabinPressureAltitude
chosen
Indicates the altitude corresponding to the current cabin air pressure, as if that pressure were the standard atmospheric pressure at that height.
-
B.
locatedAtAltitude
Indicates that an entity exists or is positioned at a specific height above a reference level, typically sea level.
-
C.
operationalAltitude
Indicates the typical or designated altitude at which an entity is intended to operate.
-
D.
meetsAtAltitude
Indicates that two or more entities come together or intersect at a specific vertical height or elevation.
-
E.
visibilityAltitude
Indicates the altitude at which something becomes visible or can be seen.
- 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_69ee812960d081909cff6085cc9fa3a6 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60e74cdf08190b753c3c10691a440 |
completed | May 2, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:01 p.m.