Triple
T2268250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo command and service module |
E50596
|
entity |
| Predicate | lastCrewedFlightDate |
P37566
|
FINISHED |
| Object | 1975-07-15 |
—
|
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: 1975-07-15 | Statement: [Apollo command and service module, lastCrewedFlightDate, 1975-07-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastCrewedFlightDate Context triple: [Apollo command and service module, lastCrewedFlightDate, 1975-07-15]
-
A.
lastCrewedLandingDate
Indicates the calendar date on which the most recent crewed landing associated with the subject took place.
-
B.
lastShuttleFlightDate
Indicates the calendar date on which the most recent shuttle flight associated with the subject took place.
-
C.
finalCommercialFlightDate
Indicates the calendar date on which an entity’s last commercial flight operation took place.
-
D.
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.
-
E.
lastCrewReturnDate
Indicates the date on which the most recent crew associated with the entity returned.
- F. None of above. chosen
Provenance (4 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_69a88b05910c8190a9a2b1ff230c85f9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc2ea65288190bc8644a07a11dfa9 |
completed | March 7, 2026, 6:17 a.m. |
| PD | Predicate disambiguation | batch_69abbdb592588190ac1ef5e8c54575b1 |
completed | March 7, 2026, 5:55 a.m. |
| PDg | Predicate description generation | batch_69abc2e97eb0819084acb26cfa4e3946 |
completed | March 7, 2026, 6:17 a.m. |
Created at: March 4, 2026, 7:48 p.m.