Triple
T38685355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISS Flight 8A |
E949100
|
entity |
| Predicate | hasTargetOrbit |
P180406
|
FINISHED |
| Object | 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: low Earth orbit | Statement: [ISS Flight 8A, hasTargetOrbit, low Earth orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTargetOrbit Context triple: [ISS Flight 8A, hasTargetOrbit, low Earth orbit]
-
A.
hasOrbit
chosen
Indicates that one entity follows a curved, typically gravitationally bound path around another entity.
-
B.
isOnOrbital
Indicates that one entity is located on or traveling along the orbital path associated with another entity.
-
C.
isOrbitalTo
Indicates that one entity moves in a curved, repeating path around another entity under the influence of a central force, typically gravity.
-
D.
hasOrbitalPlane
Indicates that one entity possesses or is associated with a specific orbital plane in which its orbit lies.
-
E.
hasAxisOfOrbit
Indicates that an orbiting object is associated with a specific axis around which its orbital motion is defined.
- 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_69f76efe16148190befd5dd59c3dfeaa |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:33 p.m.