Triple
T21461739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Molniya communications satellites |
E529487
|
entity |
| Predicate | apogeeLocation |
P144433
|
FINISHED |
| Object | over northern 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 northern hemisphere | Statement: [Molniya communications satellites, apogeeLocation, over northern hemisphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: apogeeLocation Context triple: [Molniya communications satellites, apogeeLocation, over northern hemisphere]
-
A.
apogeeUnit
Indicates the unit of measurement used to express the apogee (maximum distance or height) of an object’s trajectory or orbit.
-
B.
apexLocation
Indicates the specific point or region that serves as the highest or most pointed part (apex) of an object or structure.
-
C.
eraLocation
Indicates the place or geographic context in which a particular historical era or time period occurs or is primarily associated.
-
D.
apogeeCapability
Indicates the maximum altitude or apogee that an entity is capable of reaching or supporting.
-
E.
AVALocation
Indicates that an entity’s location is specified or associated with a particular place or spatial position.
- 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.