Triple
T28572047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | murder of William McKinley |
E723138
|
entity |
| Predicate | hasSubsequentEvent |
P47020
|
FINISHED |
| Object | death of William McKinley on 1901-09-14 |
—
|
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: death of William McKinley on 1901-09-14 | Statement: [murder of William McKinley, hasSubsequentEvent, death of William McKinley on 1901-09-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubsequentEvent Context triple: [murder of William McKinley, hasSubsequentEvent, death of William McKinley on 1901-09-14]
-
A.
hasSubsequent
chosen
Indicates that one entity occurs, appears, or is positioned after another in a defined sequence or order.
-
B.
hasPrecedingEvents
Indicates that one or more events occurred earlier in time or sequence relative to the referenced event.
-
C.
hasSubEvent
Indicates that an event is composed of, or includes as part of its structure, another event that occurs within it.
-
D.
hasSubsequentAvailability
Indicates that an entity has availability that occurs after a specified time, event, or availability period.
-
E.
hasSubsequentWork
Indicates that one work is followed by another work that continues, succeeds, or builds upon it in sequence.
- 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_69f01d7e97708190ae9e77ee66a68abd |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: April 28, 2026, 4:10 a.m.