Triple
T2169287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SCISAT-1 |
E46984
|
entity |
| Predicate | apogeeAltitude |
P18900
|
FINISHED |
| Object | approximately 650 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: approximately 650 km | Statement: [SCISAT-1, apogeeAltitude, approximately 650 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: apogeeAltitude Context triple: [SCISAT-1, apogeeAltitude, approximately 650 km]
-
A.
orbitAltitude
Indicates the height of an object's orbit above a reference body, typically measured from the body's surface or mean radius.
-
B.
reachedApogee
Indicates that an object in orbit has arrived at the highest point (apogee) in its trajectory around a central body.
-
C.
orbitApogee
chosen
Indicates the point in an orbit where an orbiting body is farthest from the central body it revolves around.
-
D.
locatedAtAltitude
Indicates that an entity exists or is positioned at a specific height above a reference level, typically sea level.
-
E.
altitudeOfRecordFlight
Indicates the altitude reached during a particular record-setting flight.
- 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_69a88a184cbc8190877791f6552c2484 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc1559ff481908efe3f214b2570dc |
completed | March 7, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69abbd9efc1c81909a65044a1ffc9038 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.