Triple
T37720466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SpX-DM1 |
E939568
|
entity |
| Predicate | reentryDateUTC |
P53922
|
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, reentryDateUTC, 2019-03-08]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reentryDateUTC Context triple: [SpX-DM1, reentryDateUTC, 2019-03-08]
-
A.
reentryDate
chosen
Indicates the date on which an entity returns or is admitted again after a prior departure, exit, or release.
-
B.
reentryOutcome
Indicates the result or consequences of an entity’s return or reentry into a system, place, or context.
-
C.
reentryBreakupDate
Indicates the date on which an object breaks apart during its reentry into an atmosphere.
-
D.
reentryProfile
Indicates the specific trajectory and conditions under which an object returns from space through an atmosphere.
-
E.
dateOfImprisonmentEnd
Indicates the date on which an entity’s period of imprisonment or incarceration comes to an end.
- 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_69fbaef0cec881908c2742d77d145901 |
completed | May 6, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.