Triple
T21305934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlas V 411 |
E525198
|
entity |
| Predicate | orbitTypes |
P7214
|
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: [Atlas V 411, orbitTypes, low Earth orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitTypes Context triple: [Atlas V 411, orbitTypes, low Earth orbit]
-
A.
orbitType
chosen
Indicates the specific kind or classification of an object's orbit in relation to the body it revolves around.
-
B.
orbitsEarth
Indicates that one object follows a gravitationally bound path around Earth as its primary central body.
-
C.
orbitsBeyond
Indicates that one celestial body orbits at a greater average distance from a central object than another specified body.
-
D.
designedForOrbitType
Indicates that something is specifically created or configured to operate within a particular type or class of orbit.
-
E.
orbits
Indicates that one object moves in a curved, usually repetitive path around another object due to a central force such as gravity.
- 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_69e0b518b8948190ad69cf9a8784d397 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75aa3f90481909b212bdbf00c2bb0 |
completed | April 21, 2026, 11:08 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:05 p.m.