Triple
T4922072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viking 1 |
E110487
|
entity |
| Predicate | landerLastContactDate |
P54757
|
FINISHED |
| Object | 1982-11-13 |
—
|
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: 1982-11-13 | Statement: [Viking 1, landerLastContactDate, 1982-11-13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landerLastContactDate Context triple: [Viking 1, landerLastContactDate, 1982-11-13]
-
A.
missionDurationToLastContact
Indicates the length of time from the mission’s start until the most recent (or final) communication contact.
-
B.
timeOfLossOfContactUTC
chosen
Indicates the specific time, expressed in Coordinated Universal Time (UTC), at which contact with an entity was lost.
-
C.
lastPrimaryRadarContactTimeLocal
Indicates the local-time timestamp when the most recent primary radar contact with the entity was recorded.
-
D.
dateOfLanding
Indicates the specific calendar date on which a landing event took place.
-
E.
lastFlight
Indicates that one flight is the final or most recent flight taken or operated by a given entity within a specified context or sequence.
- 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_69bd4413f9908190afcff44d7929cc4c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ffc2ab08190992db2400562bcee |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3421588190ab08e92b9558042e |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:30 p.m.