Triple
T7574560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westar 6 stranded in improper orbit |
E179328
|
entity |
| Predicate | actualOrbit |
P7214
|
FINISHED |
| Object | improper low Earth orbit |
—
|
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: improper low Earth orbit | Statement: [Westar 6 stranded in improper orbit, actualOrbit, improper low Earth orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actualOrbit Context triple: [Westar 6 stranded in improper orbit, actualOrbit, improper low Earth orbit]
-
A.
onOrbitalRoute
Indicates that one object is currently traveling along or positioned on a defined orbital path around another body.
-
B.
orbits
Indicates that one object moves in a curved, usually repetitive path around another object due to a central force such as gravity.
-
C.
orbitType
chosen
Indicates the specific kind or classification of an object's orbit in relation to the body it revolves around.
-
D.
coOrbitsWith
Indicates that two celestial bodies share the same or closely related orbital path around a common central object.
-
E.
orbitReference
Indicates that one entity serves as the orbital frame, path, or reference system relative to which another entity’s orbit is defined or described.
- 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_69c69f316e50819081a271c85c06f918 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f948e1e08190ad807292365a0c27 |
completed | March 27, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69c6f4de77048190b8769e717fdcf8e7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:51 p.m.