Triple
T20047948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venera 15 |
E497611
|
entity |
| Predicate | mappedRegion |
P33924
|
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 15, mappedRegion, northern hemisphere of Venus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mappedRegion Context triple: [Venera 15, mappedRegion, northern hemisphere of Venus]
-
A.
mapRegion
chosen
Indicates a relationship where a map or mapping system corresponds to, covers, or is associated with a specific geographic or logical region.
-
B.
occupiedRegion
Indicates that an entity has taken control of and is currently holding a specific geographic area or region.
-
C.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
D.
mentionsRegion
Indicates that one entity explicitly refers to or cites a specific geographic region in its content or context.
-
E.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
- 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_69da627278c88190babe4297a9df1236 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6632c085081908710cbc939ac9971 |
completed | April 20, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:37 p.m.