Triple
T19289153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adrian Rogan |
E482392
|
entity |
| Predicate | activityAtTimeOfDeath |
P17673
|
FINISHED |
| Object | watching a World Cup football match |
—
|
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: watching a World Cup football match | Statement: [Adrian Rogan, activityAtTimeOfDeath, watching a World Cup football match]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activityAtTimeOfDeath Context triple: [Adrian Rogan, activityAtTimeOfDeath, watching a World Cup football match]
-
A.
endedActivityAfterDeathOf
Indicates that an activity was terminated following, and as a consequence of, the death of a specified entity.
-
B.
deathDateEvent
Indicates the date on which a death occurred or a death-related event took place.
-
C.
diedShortlyBefore
Indicates that one entity’s death occurred a brief time before another specified event or entity’s death.
-
D.
associatedWithDeathOf
chosen
Indicates a relationship where one entity is connected in some relevant way to the death of another entity, such as by involvement, causation, or contextual association.
-
E.
diedAfter
Indicates that one entity’s death occurred later in time than another entity’s death.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc043fa481909bbe281a70fb508e |
completed | April 20, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:30 p.m.