Triple
T3296160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reginald Dyer |
E69219
|
entity |
| Predicate | notoriety |
P43479
|
FINISHED |
| Object | responsibility for mass shooting of civilians |
—
|
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: responsibility for mass shooting of civilians | Statement: [Reginald Dyer, notoriety, responsibility for mass shooting of civilians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notoriety Context triple: [Reginald Dyer, notoriety, responsibility for mass shooting of civilians]
-
A.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
B.
notableExposure
Indicates that an entity has received significant public attention, visibility, or coverage, making it notably exposed or recognized.
-
C.
popularity
Indicates how widely liked, admired, or favored something or someone is by a group of people.
-
D.
claimToFame
chosen
Indicates the notable achievement, characteristic, or association for which an entity is best known.
-
E.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
- 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_69ad859e529c8190a404273f53cb487d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb077c60c81909782be5202ce5a43 |
completed | March 8, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69ada42407dc81909f60d7a14e1b7934 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.