Triple
T20030320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shipton-on-Cherwell train crash |
E495103
|
entity |
| Predicate | happenedOn |
P58129
|
FINISHED |
| Object | Christmas Eve 1874 |
—
|
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: Christmas Eve 1874 | Statement: [Shipton-on-Cherwell train crash, happenedOn, Christmas Eve 1874]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: happenedOn Context triple: [Shipton-on-Cherwell train crash, happenedOn, Christmas Eve 1874]
-
A.
eventOccurredAt
chosen
Indicates that a particular event took place at a specific time or location.
-
B.
occurredDuring
Indicates that one event or action took place within the temporal span of another event or time period.
-
C.
injuryOccurredAt
Indicates that an injury took place at a specific location or during a particular event or time.
-
D.
appointedOn
Indicates the specific date or time at which an entity is formally assigned or designated to a role, position, or responsibility.
-
E.
occursOnOrAround
Indicates that an event or action takes place on a specific date or within a small, approximate time window surrounding that date.
- 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66291a00c8190b0b895909f32d623 |
completed | April 20, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69e54ce752748190a0a1ffddd0372271 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:36 p.m.