Triple
T8673627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Launch Demo 2 |
E205859
|
entity |
| Predicate | launchFromAircraftAltitudeApprox |
P68744
|
FINISHED |
| Object | 35000 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: 35000 ft | Statement: [Launch Demo 2, launchFromAircraftAltitudeApprox, 35000 ft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchFromAircraftAltitudeApprox Context triple: [Launch Demo 2, launchFromAircraftAltitudeApprox, 35000 ft]
-
A.
aircraftHeight
chosen
Indicates the vertical distance or altitude of an aircraft relative to a reference level (such as ground or sea level).
-
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.
explosionAltitude
Indicates the height above a reference surface at which an explosion occurs or is triggered.
-
E.
landingDistance
Indicates the required or actual distance needed for an aircraft or object to complete a landing from approach to full stop.
- 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_69ca83529a9c8190b5c075b4f14636ed |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4ae6d19c8190be003f7901c0468d |
completed | March 31, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69cc4567b5c881908d9ec5dcfc783fac |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:31 p.m.