Triple
T16257501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venus Express |
E394668
|
entity |
| Predicate | contactLostDate |
P54757
|
FINISHED |
| Object | 2014-11-28 |
—
|
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: 2014-11-28 | Statement: [Venus Express, contactLostDate, 2014-11-28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contactLostDate Context triple: [Venus Express, contactLostDate, 2014-11-28]
-
A.
lostFunctionDate
Indicates the date on which a function, capability, or operational role ceased to be active or usable.
-
B.
lastSignalDate
Indicates the date on which the most recent signal or communication event occurred between the related entities.
-
C.
lastSpeechDate
Indicates the date on which an entity most recently gave or delivered a speech.
-
D.
lastSeenOn
Indicates the most recent time or date at which the subject entity was observed, detected, or recorded.
-
E.
timeOfLossOfContactUTC
chosen
Indicates the specific time, expressed in Coordinated Universal Time (UTC), at which contact with an entity was lost.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2459b1624819086bf681075097235 |
completed | April 17, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.