Triple
T16921286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martian Moons eXploration mission |
E410448
|
entity |
| Predicate | plannedSampleReturnDate |
P112129
|
FINISHED |
| Object | early 2030s |
—
|
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: early 2030s | Statement: [Martian Moons eXploration mission, plannedSampleReturnDate, early 2030s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedSampleReturnDate Context triple: [Martian Moons eXploration mission, plannedSampleReturnDate, early 2030s]
-
A.
timeOfReturn
chosen
Indicates the specific time at which an entity comes back to a prior location or state.
-
B.
dateOfReturnAsResidence
Indicates the date on which an entity returned to a particular place to resume or establish it as their residence.
-
C.
deliveryDate
Indicates the specific date on which a product, service, or item is scheduled or expected to be delivered.
-
D.
subsequentArrivalDate
Indicates that one entity’s arrival date occurs after the arrival date of another related entity.
-
E.
recommendedDate
Indicates the date on which something is advised or suggested to occur, be used, or be acted upon.
- 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cdee252c81908621b2ca897416e9 |
completed | April 18, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69e32b982f548190b08414d55810de19 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.