Triple
T16973548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landsat 6 |
E411748
|
entity |
| Predicate | intendedOrbitAltitude |
P12741
|
FINISHED |
| Object | 705 km |
—
|
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: 705 km | Statement: [Landsat 6, intendedOrbitAltitude, 705 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedOrbitAltitude Context triple: [Landsat 6, intendedOrbitAltitude, 705 km]
-
A.
orbitAltitude
chosen
Indicates the height of an object's orbit above a reference body, typically measured from the body's surface or mean radius.
-
B.
locatedAtAltitude
Indicates that an entity exists or is positioned at a specific height above a reference level, typically sea level.
-
C.
targetOrbitInclination
Indicates the angle between an object's orbital plane and a reference plane (such as the equatorial or ecliptic plane) for its target orbit.
-
D.
KármánLineAltitude
Indicates that the specified altitude corresponds to the Kármán line, the conventional boundary between Earth's atmosphere and outer space.
-
E.
operationalAltitude
Indicates the typical or designated altitude at which an entity is intended to operate.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0af06688190a77682aa297cd27e |
completed | April 18, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:31 a.m.