Triple
T21461740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Molniya communications satellites |
E529487
|
entity |
| Predicate | perigeeLocation |
P144434
|
FINISHED |
| Object | over southern hemisphere |
—
|
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: over southern hemisphere | Statement: [Molniya communications satellites, perigeeLocation, over southern hemisphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perigeeLocation Context triple: [Molniya communications satellites, perigeeLocation, over southern hemisphere]
-
A.
perigee
Indicates the point in an object's orbit where it is closest to the body it is orbiting.
-
B.
perihelionLocation
Indicates the location in space where an orbiting body is at its closest point to the Sun (its perihelion).
-
C.
perihelionDate
Indicates the date on which an orbiting body reaches its closest point to the Sun in its orbital path.
-
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.
closestApproachToMoon
Indicates the point or distance at which an object comes nearest to the Moon along its trajectory or orbit.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e63d2aca38819094d312078feaa436 |
completed | April 20, 2026, 2:50 p.m. |
Created at: April 16, 2026, 6:09 p.m.