Triple
T20002402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venera 13 |
E494365
|
entity |
| Predicate | designedSurfaceLifetime |
P8105
|
FINISHED |
| Object | 32 minutes |
—
|
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: 32 minutes | Statement: [Venera 13, designedSurfaceLifetime, 32 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedSurfaceLifetime Context triple: [Venera 13, designedSurfaceLifetime, 32 minutes]
-
A.
designLifetime
chosen
Indicates the intended duration or operational period for which something is designed to function as specified.
-
B.
hasMeanLifetime
Indicates the characteristic average time duration for which an entity, state, or condition persists before it decays, ends, or changes.
-
C.
exceededDesignLifetime
Indicates that an entity has operated beyond the duration or usage limits specified in its original design.
-
D.
designedForLifecycle
Indicates that something has been intentionally created or configured to support, align with, or optimize a particular lifecycle or set of lifecycle stages.
-
E.
serviceLifeTarget
Indicates the intended or planned duration of time that a service, asset, or component is expected to remain in use or perform its function.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e661a2e34481908a495cc5d077c41f |
completed | April 20, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:33 p.m.