Triple
T16921627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TANSO-CAI |
E410455
|
entity |
| Predicate | hostSatelliteOrbitAltitude |
P12741
|
FINISHED |
| Object | about 666 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: about 666 km | Statement: [TANSO-CAI, hostSatelliteOrbitAltitude, about 666 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostSatelliteOrbitAltitude Context triple: [TANSO-CAI, hostSatelliteOrbitAltitude, about 666 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.
locatedInOrbitAbove
Indicates that one entity is positioned in an orbital path around and above another entity.
-
C.
locatedAtAltitude
Indicates that an entity exists or is positioned at a specific height above a reference level, typically sea level.
-
D.
satelliteLocation
Indicates that one entity is located in orbit around or positioned relative to another celestial body or reference point, as a satellite.
-
E.
orbitApogee
Indicates the point in an orbit where an orbiting body is farthest from the central body it revolves around.
- 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cdef7df881908b69aa3c4f50ef94 |
completed | April 18, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69e32b982f548190b08414d55810de19 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.