Triple
T14201867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anti-sacrilege law |
E351982
|
entity |
| Predicate | victimClass |
P87855
|
FINISHED |
| Object | religious sensibilities of Catholics |
—
|
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: religious sensibilities of Catholics | Statement: [Anti-sacrilege law, victimClass, religious sensibilities of Catholics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: victimClass Context triple: [Anti-sacrilege law, victimClass, religious sensibilities of Catholics]
-
A.
victimGroup
Indicates that one group or entity is the target or recipient of harm, abuse, or wrongdoing caused by another.
-
B.
victimGroupContext
chosen
Indicates the contextual circumstances or setting in which a victim group is targeted, affected, or involved in an event or action.
-
C.
victimGroupHelped
Indicates that assistance, support, or aid was provided to a group identified as victims.
-
D.
victimAge
Indicates the age of the person who is the victim in the described event or situation.
-
E.
victimRole
Indicates that one entity participates in an event or situation specifically in the role of the victim or harmed party.
- 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_69d827894ac0819097803e57f3227b23 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61f589a08190b71ad4e69d92ffd0 |
completed | April 14, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69de05bcd7d48190a4848d9320404aa6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:05 a.m.