Triple
T37514095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zakarum faith |
E932588
|
entity |
| Predicate | hasHolyWar |
P196732
|
FINISHED |
| Object | crusades against perceived heretics |
—
|
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: crusades against perceived heretics | Statement: [Zakarum faith, hasHolyWar, crusades against perceived heretics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHolyWar Context triple: [Zakarum faith, hasHolyWar, crusades against perceived heretics]
-
A.
hasReligionOfBelligerents
Indicates that the belligerent parties in a conflict are associated with a particular religion or religious affiliation.
-
B.
hasWarDeity
Indicates that an entity has a specific deity associated with war as part of its religious or mythological system.
-
C.
isHolierThan
Indicates that one entity is considered more sacred, morally pure, or spiritually superior than another.
-
D.
hasNotableWar
Indicates that an entity is associated with a significant or historically important war.
-
E.
hasFictionalWar
Indicates that there exists a fictional or imagined war involving the related entities.
- F. None of above. chosen
Provenance (4 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe629b4fa481908467c7c41b77f0c6 |
completed | May 8, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69fe61bb260c819083f9378a3a06ca47 |
completed | May 8, 2026, 10:20 p.m. |
| PDg | Predicate description generation | batch_69fe629a8d4c8190b4aa4dee39efc0a6 |
completed | May 8, 2026, 10:24 p.m. |
Created at: May 3, 2026, 4:17 p.m.