Triple
T19612014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venera 1 |
E470755
|
entity |
| Predicate | closestApproachDistanceToVenus_km |
P59619
|
FINISHED |
| Object | approximately 100000 |
—
|
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: approximately 100000 | Statement: [Venera 1, closestApproachDistanceToVenus_km, approximately 100000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closestApproachDistanceToVenus_km Context triple: [Venera 1, closestApproachDistanceToVenus_km, approximately 100000]
-
A.
closestApproachDistance
chosen
Indicates the minimum distance between two entities at the point where they come closest to each other during their motion or interaction.
-
B.
closestApproachToPlutoDistance
Indicates the minimum distance an object comes to Pluto at the point of its closest approach.
-
C.
closestApproachDistanceToJupiter
Indicates the minimum distance an object comes to Jupiter during its trajectory or orbit.
-
D.
closestApproachToSaturnDistance
Indicates the minimum distance an object comes to Saturn at its point of closest approach.
-
E.
arrivalAtVenus
Indicates the event or state of something reaching or entering Venus as its destination.
- 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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640cbeda08190addb1adf84af4993 |
completed | April 20, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69e514e166dc8190a0f147e0b4c8bbe7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.