Triple
T13514585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luna 20 |
E322725
|
entity |
| Predicate | returnDateToEarth |
P37335
|
FINISHED |
| Object | 1972-02-25 |
—
|
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: 1972-02-25 | Statement: [Luna 20, returnDateToEarth, 1972-02-25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnDateToEarth Context triple: [Luna 20, returnDateToEarth, 1972-02-25]
-
A.
returnToEarthDateUTC
chosen
Indicates the date and time, in Coordinated Universal Time (UTC), when something or someone is scheduled or expected to return to Earth.
-
B.
timeOnEarth
Indicates the duration that an entity has spent on Earth, typically measured as elapsed time from arrival or birth.
-
C.
dateOfReturnAsResidence
Indicates the date on which an entity returned to a particular place to resume or establish it as their residence.
-
D.
lastCrewReturnDate
Indicates the date on which the most recent crew associated with the entity returned.
-
E.
transportedToEarthBy
Indicates that an entity was moved or carried from another location or context to Earth by a specified agent or means.
- 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf87ca288190a147fbdb2f90985f |
completed | April 12, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69dbae0b63748190b5e207f84b2532ea |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:44 p.m.