Triple
T19731934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venera 3 |
E473875
|
entity |
| Predicate | impactStatus |
P137129
|
FINISHED |
| Object | successful impact |
—
|
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: successful impact | Statement: [Venera 3, impactStatus, successful impact]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactStatus Context triple: [Venera 3, impactStatus, successful impact]
-
A.
impactOutcome
Indicates that one entity produces an effect or influence that changes the result, consequence, or final state of another entity or situation.
-
B.
impactDescription
Indicates a description of the effect, consequence, or influence that one entity, action, or event has on another.
-
C.
impactIfCompleted
Indicates the effect or consequence that will occur if the referenced task or action is fully completed.
-
D.
impactEvent
Indicates that one entity physically strikes or collides with another, producing a resulting effect or change.
-
E.
impactOrigin
Indicates that one entity is the source or cause from which the impact or effect on another entity originates.
- F. None of above. chosen
Provenance (4 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e649fd18148190a6e85b2be0069dde |
completed | April 20, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69e5304a7aac8190ac13f75f0c008e45 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:47 p.m.