Triple
T26964122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Press |
E679124
|
entity |
| Predicate | hasOriginalRunEndDate |
P118268
|
FINISHED |
| Object | 2018-10-11 |
—
|
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: 2018-10-11 | Statement: [Press, hasOriginalRunEndDate, 2018-10-11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalRunEndDate Context triple: [Press, hasOriginalRunEndDate, 2018-10-11]
-
A.
hasCollectionEndDate
Indicates the date on which a collection activity, period, or process is scheduled or recorded to end.
-
B.
hasExecutionDate
Indicates that an entity is associated with a specific date on which an execution or carrying out of an action, order, or sentence is scheduled or took place.
-
C.
hasTemporalEnd
chosen
Indicates that an event, state, or process concludes or terminates at a specific point or interval in time.
-
D.
originalRunStatus
Indicates the initial or prior execution state of a run before any subsequent updates or changes.
-
E.
originalScheduleEndDate
Indicates the date on which a planned or initial schedule was originally intended to 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 27, 2026, 6:34 a.m.