Triple
T1565681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Shuttle Main Engines |
E33426
|
entity |
| Predicate | lastShuttleFlightDate |
P29519
|
FINISHED |
| Object | 2011-07-08 |
—
|
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: 2011-07-08 | Statement: [Space Shuttle Main Engines, lastShuttleFlightDate, 2011-07-08]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastShuttleFlightDate Context triple: [Space Shuttle Main Engines, lastShuttleFlightDate, 2011-07-08]
-
A.
lastCrewedLandingDate
Indicates the calendar date on which the most recent crewed landing associated with the subject took place.
-
B.
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.
-
C.
lastCrewReturnDate
Indicates the date on which the most recent crew associated with the entity returned.
-
D.
nextShuttleFlightAfterDisaster
Indicates the first shuttle flight that took place after a specified disaster event.
-
E.
spaceflightEndDate
Indicates the date on which a particular spaceflight or space mission concludes or is officially terminated.
- 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_69a885f11b048190935025a035302715 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90fccd4b48190a44012888a00af7f |
completed | March 5, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69a907b872f0819096b3df6ad502c63e |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a90fcb8ca48190a9ee50559ba73b22 |
completed | March 5, 2026, 5:08 a.m. |
Created at: March 4, 2026, 7:27 p.m.