Triple
T37720467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SpX-DM1 |
E939568
|
entity |
| Predicate | splashdownDateUTC |
P181371
|
FINISHED |
| Object | 2019-03-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: 2019-03-08 | Statement: [SpX-DM1, splashdownDateUTC, 2019-03-08]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: splashdownDateUTC Context triple: [SpX-DM1, splashdownDateUTC, 2019-03-08]
-
A.
shotDownDate
Indicates the date on which an entity was shot down, such as an aircraft or missile being brought down from the air.
-
B.
missionSplashdownDateUTC
chosen
Indicates the date and time, in Coordinated Universal Time (UTC), when a mission’s splashdown (water landing) occurred.
-
C.
launchEndDate
Indicates the date on which a launch activity or campaign is completed or comes to an end.
-
D.
launchDate
Indicates the date on which an entity (such as a product, service, or project) is officially released or made available.
-
E.
landingDate
Indicates the date on which an entity arrives at or touches down on a specified destination or surface.
- 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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:18 p.m.