Triple
T863132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bloody Sunday (1972) |
E18640
|
entity |
| Predicate | hasInquiryEndDate |
P140
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Bloody Sunday (1972), hasInquiryEndDate, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInquiryEndDate Context triple: [Bloody Sunday (1972), hasInquiryEndDate, 2010]
-
A.
hasDeadline
Indicates that an entity is associated with a specific due date or time by which it must be completed or fulfilled.
-
B.
concludedAfter
Indicates that one event or process finishes at a time later than the completion of another event or process.
-
C.
endDate
chosen
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
D.
concludedAt
Indicates the point in time at which an event, process, or relationship comes to an end or is completed.
-
E.
typicalEndDate
Indicates the date on which something, such as an event, process, or period, normally or customarily ends.
- 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_69a4938ce8688190a24bdfef82ba7d21 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac67d4d481909487d3edb3e46936 |
completed | March 1, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69a4aa86065881909d477e26fdd84d45 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.