Triple
T20114599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venera 11 |
E490423
|
entity |
| Predicate | descentParachute |
P116289
|
FINISHED |
| Object | used in upper atmosphere |
—
|
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: used in upper atmosphere | Statement: [Venera 11, descentParachute, used in upper atmosphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: descentParachute Context triple: [Venera 11, descentParachute, used in upper atmosphere]
-
A.
parachuteType
Indicates the specific kind or category of parachute associated with an entity or event.
-
B.
parachuteSystem
Indicates that one entity functions as a parachute system used to safely decelerate or recover another entity.
-
C.
parachuteStatus
Indicates the current condition or operational state of a parachute in relation to its use or deployment.
-
D.
descentVia
Indicates a lineage relationship where one entity is descended from another through one or more intermediate generations or branches.
-
E.
typicalUseOnDescent
chosen
Indicates that an object or procedure is commonly used during the descent phase of an activity, operation, or journey.
- 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_69da62636cc08190982cc71733a17b8d |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e666e3f2288190840d1eb431ac9a1b |
completed | April 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:29 p.m.