Triple
T12579762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venera 9 |
E300302
|
entity |
| Predicate | landingHemisphere |
P70356
|
FINISHED |
| Object | northern hemisphere of Venus |
—
|
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: northern hemisphere of Venus | Statement: [Venera 9, landingHemisphere, northern hemisphere of Venus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landingHemisphere Context triple: [Venera 9, landingHemisphere, northern hemisphere of Venus]
-
A.
hemisphereName
chosen
Indicates the named hemisphere (e.g., northern, southern, eastern, or western) that a given location or entity belongs to.
-
B.
hemispherePresence
Indicates the spatial relationship of whether and in which hemisphere(s) (e.g., northern, southern, eastern, western) an entity is present or occurs.
-
C.
landingRegion
Indicates the area or zone where an object or entity comes to rest or makes contact after moving or descending.
-
D.
locatedInWesternHemisphere
Indicates that the subject is geographically situated within the Western Hemisphere of the Earth.
-
E.
visibleInHemisphere
Indicates that an object or phenomenon can be seen or observed from a specified hemisphere of a celestial body.
- 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_69d7bde87b648190bcd0266e9efde098 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954e6e20481908bca684c4b497c48 |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95416cbd88190b2c65196162349bc |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5 p.m.