Triple
T17121522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N348MS |
E415476
|
entity |
| Predicate | launchAltitudeRange |
P109129
|
FINISHED |
| Object | approximately 13–15 kilometers |
—
|
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: approximately 13–15 kilometers | Statement: [N348MS, launchAltitudeRange, approximately 13–15 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchAltitudeRange Context triple: [N348MS, launchAltitudeRange, approximately 13–15 kilometers]
-
A.
flightLevelRange
Indicates the range of permissible or actual flight levels associated with an aircraft’s operation or a specific flight segment.
-
B.
operationalAltitude
Indicates the typical or designated altitude at which an entity is intended to operate.
-
C.
extendsToApproximateAltitude
chosen
Indicates that something reaches or stretches up to a specified altitude value, which is understood to be approximate rather than exact.
-
D.
extendsFromAltitude
Indicates a relationship where something stretches or reaches outward starting from a specified altitude.
-
E.
altitudeRange_m
Indicates the range of altitudes, measured in meters, over which the relationship or condition holds.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3e809ee888190a2cf69d59c0b9c20 |
completed | April 18, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69e35d6d20808190a38bb32e2294bc48 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:36 a.m.