Triple
T19908875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venera 5 |
E478490
|
entity |
| Predicate | precededBy |
P97
|
FINISHED |
| Object | Venera 4 |
—
|
NE NERFINISHED |
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: Venera 4 | Statement: [Venera 5, precededBy, Venera 4]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Venera 4 Context triple: [Venera 5, precededBy, Venera 4]
-
A.
Venera 4
chosen
Venera 4 was a Soviet space probe that became the first spacecraft to successfully enter another planet’s atmosphere and transmit in-situ data, specifically from Venus, in 1967.
-
B.
Venera 5
Venera 5 was a Soviet space probe launched in 1969 as part of the Venera program to study the atmosphere and surface conditions of Venus.
-
C.
Venera 3
Venera 3 was a Soviet space probe that became the first human-made object to impact the surface of another planet, Venus, in 1966.
-
D.
Venera 2
Venera 2 was a Soviet space probe launched in 1965 as part of the Venera program, intended to conduct a flyby of Venus but lost communication before returning scientific data.
-
E.
Venera 8
Venera 8 was a Soviet space probe that successfully landed on Venus in 1972 and transmitted data from its surface, contributing significantly to early Venus exploration.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e520682081909892916424699bd5 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6598d91ac8190be6abdd7d1542aec |
completed | April 20, 2026, 4:51 p.m. |
Created at: April 10, 2026, 1:53 p.m.