Triple
T38199813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mars 7 |
E1009020
|
entity |
| Predicate | approachDate |
P13779
|
FINISHED |
| Object | 1974-03-09 |
—
|
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: 1974-03-09 | Statement: [Mars 7, approachDate, 1974-03-09]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approachDate Context triple: [Mars 7, approachDate, 1974-03-09]
-
A.
dateApproximate
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
B.
recommendedDate
Indicates the date on which something is advised or suggested to occur, be used, or be acted upon.
-
C.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
D.
closestApproachDate
chosen
Indicates the date on which two entities come nearest to each other in space or position.
-
E.
approximateDateChange
Indicates that the date associated with an entity has changed in an inexact or estimated manner rather than to a precisely known new date.
- 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_69f76dc94fcc8190bd2f55e81f9d6527 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fff4530f908190afe9387f732c2b7e |
completed | May 10, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fff3c01a64819091196875b0c88607 |
completed | May 10, 2026, 2:56 a.m. |
Created at: May 3, 2026, 4:30 p.m.