Triple
T10058540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Shuttle |
E208923
|
entity |
| Predicate | ColumbiaDisasterDate |
P12735
|
FINISHED |
| Object | 2003-02-01 |
—
|
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: 2003-02-01 | Statement: [Space Shuttle, ColumbiaDisasterDate, 2003-02-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ColumbiaDisasterDate Context triple: [Space Shuttle, ColumbiaDisasterDate, 2003-02-01]
-
A.
Columbia disaster
Indicates the relationship of being involved in, affected by, or causally connected to the Space Shuttle Columbia disaster event.
-
B.
Apollo13IncidentDate
Indicates the specific calendar date on which the Apollo 13 incident occurred.
-
C.
missionAccidentDate
chosen
Indicates the date on which an accident occurred during or in relation to a mission.
-
D.
firstLunarLandingDate
Indicates the calendar date on which an entity’s first lunar landing occurred.
-
E.
firstOrbitalLaunchAttemptDate
Indicates the calendar date on which an entity made its first attempt to launch a vehicle into orbit.
- 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_69ca836094408190a36a1ea7e9a86fcd |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcfb0f17c8190a8c0cfb02863537d |
completed | April 2, 2026, 2:08 a.m. |
| PD | Predicate disambiguation | batch_69cd4b92573481909389bc6148ae7ea8 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:57 p.m.