Triple
T5929826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunday Bloody Sunday |
E131906
|
entity |
| Predicate | isProtestSongAgainst |
P13334
|
FINISHED |
| Object | sectarian violence |
—
|
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: sectarian violence | Statement: [Sunday Bloody Sunday, isProtestSongAgainst, sectarian violence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isProtestSongAgainst Context triple: [Sunday Bloody Sunday, isProtestSongAgainst, sectarian violence]
-
A.
repressedDissent
Indicates that one party has actively suppressed or stifled opposition, criticism, or disagreement from another party or group.
-
B.
protests
chosen
Indicates that an entity publicly expresses opposition or disapproval toward another entity, action, or situation.
-
C.
meansOfStruggle
Indicates the method, tactic, or form of action used by an entity in carrying out a struggle or conflict.
-
D.
notableProtest
Indicates that an entity is recognized for having led, organized, or been centrally involved in a significant protest or demonstration.
-
E.
struggleFor
Indicates a relationship where one entity exerts effort or engages in conflict in order to obtain, achieve, or defend another entity or goal.
- 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_69c0085b75e88190a632f9691f9da48b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03c9239e08190bff7ef2bd6d21ae0 |
completed | March 22, 2026, 7:01 p.m. |
| PD | Predicate disambiguation | batch_69c033541d108190a34d1fde2fe9dacb |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4 p.m.