Triple
T21461562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Molniya orbit |
E529484
|
entity |
| Predicate | apoapsisLocation |
P18900
|
FINISHED |
| Object | high northern latitudes above Earth |
—
|
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: high northern latitudes above Earth | Statement: [Molniya orbit, apoapsisLocation, high northern latitudes above Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: apoapsisLocation Context triple: [Molniya orbit, apoapsisLocation, high northern latitudes above Earth]
-
A.
apoapsisType
Indicates the specific kind or classification of an orbit’s apoapsis (farthest point from the central body) associated with an entity.
-
B.
apoapsisBody
Indicates the celestial body that an orbiting object is farthest from at its apoapsis.
-
C.
orbitApogee
chosen
Indicates the point in an orbit where an orbiting body is farthest from the central body it revolves around.
-
D.
hasAphelionNear
Indicates that one celestial body's aphelion (its farthest point from the object it orbits) lies close to another specified reference point or object.
-
E.
aphelionDistance
Indicates the greatest distance between an orbiting body and the star it orbits, measured at the point of aphelion in its orbit.
- 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_69e0c458133481908ae8b41a12c4edec |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9e9ef0c0881908554977df00604a6 |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:09 p.m.