Triple
T2054632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mission: SPACE |
E45645
|
entity |
| Predicate | sponsorEndDate_HP |
P35615
|
FINISHED |
| Object | 2015-09-30 |
—
|
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: 2015-09-30 | Statement: [Mission: SPACE, sponsorEndDate_HP, 2015-09-30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sponsorEndDate_HP Context triple: [Mission: SPACE, sponsorEndDate_HP, 2015-09-30]
-
A.
extendedSupportEndDate
Indicates the date on which an extended support period for something ends.
-
B.
typicalEndDate
Indicates the date on which something, such as an event, process, or period, normally or customarily ends.
-
C.
deFactoEndDate
Indicates the date on which a relationship, status, or condition effectively ended in practice, regardless of any formal or official end date.
-
D.
endDate
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
E.
sponsorInHouse
Indicates that one entity formally supports, promotes, or funds another entity within the same organization, institution, or internal setting.
- 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_69a8891a19508190a12ef1e192308dcb |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9a8518081909ba95a8ef9321f12 |
completed | March 7, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_69abb7abba508190b872f345d3ba51bb |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb94ec400819097596732aabed854 |
completed | March 7, 2026, 5:36 a.m. |
Created at: March 4, 2026, 7:40 p.m.