Triple
T20095244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venera 14 |
E496381
|
entity |
| Predicate | actualSurfaceOperationTime |
P40756
|
FINISHED |
| Object | on the order of an hour |
—
|
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: on the order of an hour | Statement: [Venera 14, actualSurfaceOperationTime, on the order of an hour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actualSurfaceOperationTime Context triple: [Venera 14, actualSurfaceOperationTime, on the order of an hour]
-
A.
surfaceOperationsDuration
Indicates the length of time that surface-related operations or activities are carried out.
-
B.
actualDuration
chosen
Indicates the real amount of time that an event, process, or activity actually took to complete, as opposed to its planned or estimated duration.
-
C.
hasSurfaceOperations
Indicates that an entity performs, supports, or is associated with activities or operations occurring on a surface.
-
D.
surfaceOperation
Indicates an operation or activity that is performed on or at the surface of an object, material, or environment.
-
E.
executionSurface
Indicates the surface or medium on which an action, process, or operation is carried out or executed.
- 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_69da626eee3881909f3454986d4a6511 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6666b891c8190b4e4a60b73728771 |
completed | April 20, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:24 p.m.