Triple
T12475197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venera 7 |
E298157
|
entity |
| Predicate | landingDuration |
P38392
|
FINISHED |
| Object | about 23 minutes of data from Venus surface |
—
|
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 23 minutes of data from Venus surface | Statement: [Venera 7, landingDuration, about 23 minutes of data from Venus surface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landingDuration Context triple: [Venera 7, landingDuration, about 23 minutes of data from Venus surface]
-
A.
landingVelocity
Indicates the speed at which an object or entity is moving at the moment it makes contact with a surface or completes its descent.
-
B.
landing
chosen
Indicates the action or event of an entity coming down from the air or a higher position to make controlled contact with a surface.
-
C.
locationPeriod
Indicates that an entity is associated with being at a particular location during a specified time period.
-
D.
landingRequires
Indicates that performing a landing action is contingent upon satisfying a specified requirement or precondition.
-
E.
laterDuration
Indicates that one event or time interval occurs after another and lasts for a specified duration.
- 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_69d6ada270808190b1a2b2e7b02bb426 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e626dbc8190ac7dcdb542ba9b0c |
completed | April 10, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69d94d3f701c81909dd0e00251ac8553 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:56 p.m.