Triple
T12579766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venera 9 |
E300302
|
entity |
| Predicate | surfaceOperationDuration |
P99865
|
FINISHED |
| Object | about 53 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: about 53 minutes | Statement: [Venera 9, surfaceOperationDuration, about 53 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceOperationDuration Context triple: [Venera 9, surfaceOperationDuration, about 53 minutes]
-
A.
surfaceOperationsDuration
chosen
Indicates the length of time that surface-related operations or activities are carried out.
-
B.
surfaceOperation
Indicates an operation or activity that is performed on or at the surface of an object, material, or environment.
-
C.
roofOperationTime
Indicates the duration or specific time period during which a roof-related operation or mechanism is active or performed.
-
D.
surfaceManagement
Indicates the management or control exercised over the surface of an area, object, or environment, such as its use, maintenance, or treatment.
-
E.
surfaceAccess
Indicates that one entity provides a means for another entity to reach, enter, or interact with a surface or outer layer.
- 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_69d7bde87b648190bcd0266e9efde098 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954e6e20481908bca684c4b497c48 |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95416cbd88190b2c65196162349bc |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5 p.m.