Triple
T14151417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falcon 10X |
E350690
|
entity |
| Predicate | maximumCabinAltitude_ft |
P75760
|
FINISHED |
| Object | 3000 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: 3000 at 41000 ft | Statement: [Falcon 10X, maximumCabinAltitude_ft, 3000 at 41000 ft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumCabinAltitude_ft Context triple: [Falcon 10X, maximumCabinAltitude_ft, 3000 at 41000 ft]
-
A.
cabinPressureAltitude
Indicates the altitude corresponding to the current cabin air pressure, as if that pressure were the standard atmospheric pressure at that height.
-
B.
altitudeCapability
Indicates the maximum or typical altitude at which an entity can effectively operate or function.
-
C.
operationalAltitude
Indicates the typical or designated altitude at which an entity is intended to operate.
-
D.
altitudeOfRecordFlight
Indicates the altitude reached during a particular record-setting flight.
-
E.
serviceCeilingFeet
chosen
Indicates the maximum altitude, measured in feet, at which an aircraft or vehicle can effectively operate or provide service.
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6124e23481909e5132a40a1d8624 |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:57 a.m.