Triple
T19651739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venera 2 |
E471830
|
entity |
| Predicate | missionDurationUntilContactLost |
P13785
|
FINISHED |
| Object | about 3.5 months |
—
|
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: about 3.5 months | Statement: [Venera 2, missionDurationUntilContactLost, about 3.5 months]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionDurationUntilContactLost Context triple: [Venera 2, missionDurationUntilContactLost, about 3.5 months]
-
A.
missionDurationToLastContact
chosen
Indicates the length of time from the mission’s start until the most recent (or final) communication contact.
-
B.
timeOfLossOfContactUTC
Indicates the specific time, expressed in Coordinated Universal Time (UTC), at which contact with an entity was lost.
-
C.
missionDuration
Indicates the length of time over which a mission or operation takes place from start to finish.
-
D.
missionDurationFromLaunchToImpact
Indicates the total elapsed time between the launch of a mission and the moment of its impact.
-
E.
missionDurationCapability
Indicates the length of time an entity is capable of sustaining or performing a mission or operation.
- 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e64141f61c819098fe148581fb1747 |
completed | April 20, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.