Triple
T34371799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Kersey |
E882175
|
entity |
| Predicate | reactionToTragedy |
P94298
|
FINISHED |
| Object | becomes vigilante |
—
|
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: becomes vigilante | Statement: [Paul Kersey, reactionToTragedy, becomes vigilante]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reactionToTragedy Context triple: [Paul Kersey, reactionToTragedy, becomes vigilante]
-
A.
fatherReactionToDeath
Indicates the emotional or behavioral response of a father to the death of someone (typically a close relation).
-
B.
otherMajorTragedy
chosen
Indicates that the subject experienced or was involved in a significant tragic event other than the primary or most notable tragedy under consideration.
-
C.
reactionToPatricide
Indicates the emotional or behavioral response of an entity to the act of killing one’s own father.
-
D.
causedReaction
Indicates that one entity’s action or state brought about a specific reaction or response in another entity.
-
E.
reactionToWar
Indicates how an entity responds emotionally, behaviorally, or attitudinally to a war or armed conflict.
- 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_69f349bf5d7481908dd5da4cbdf74047 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:59 a.m.