Triple
T9386035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Terror |
E225906
|
entity |
| Predicate | depictsConflictType |
P9742
|
FINISHED |
| Object | ideological conflict |
—
|
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: ideological conflict | Statement: [Holy Terror, depictsConflictType, ideological conflict]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depictsConflictType Context triple: [Holy Terror, depictsConflictType, ideological conflict]
-
A.
depictsConflict
chosen
Indicates that one entity visually represents or portrays a situation of conflict involving another entity or entities.
-
B.
conflictType
Indicates the specific kind or category of conflict that characterizes the relationship or interaction between entities.
-
C.
conflictDescribedIn
Indicates that a particular conflict is documented, detailed, or discussed within a specified information source or description.
-
D.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
E.
conflictSpecific
Indicates a specific, concrete instance or type of conflict that exists between the related entities.
- 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_69ca842e9dcc8190a264119e683cfe04 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd50d3964c8190b0353f56df755db8 |
completed | April 1, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69cca53bd6ec81909bf403ce304e5c08 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:44 p.m.