Triple
T33869711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Attica Prison uprising |
E868165
|
entity |
| Predicate | initiallyBlamedOn |
P871
|
FINISHED |
| Object | inmates |
—
|
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: inmates | Statement: [Attica Prison uprising, initiallyBlamedOn, inmates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initiallyBlamedOn Context triple: [Attica Prison uprising, initiallyBlamedOn, inmates]
-
A.
blamedOn
Indicates that responsibility or fault for something is assigned to a particular entity.
-
B.
firstAccused
chosen
Indicates that the subject is the primary or earliest individual formally charged or blamed in a particular case or incident.
-
C.
wronglyAccusedBy
Indicates that one entity has falsely or unjustly accused another entity of wrongdoing.
-
D.
allegedVictimOf
Indicates that one entity is claimed or reported to have been harmed, wronged, or victimized by another entity, without asserting that the claim is proven.
-
E.
initiatedBecauseOf
Indicates that one event, action, or process was started as a direct result of, or in response to, another specified cause or condition.
- 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_69f34995029081909ede0f7df73d1a5e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: May 1, 2026, 1:47 a.m.