Triple
T38515541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Age of Religious Wars |
E922332
|
entity |
| Predicate | hasMainConflictType |
P68124
|
FINISHED |
| Object | religious war |
—
|
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 war | Statement: [Age of Religious Wars, hasMainConflictType, religious war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainConflictType Context triple: [Age of Religious Wars, hasMainConflictType, religious war]
-
A.
hasPrimaryConflictType
chosen
Indicates that an entity is associated with its main or most significant type of conflict among possible conflict categories.
-
B.
hasPotentialConflictType
Indicates that there exists a possible or anticipated type of conflict associated with the given entity or relationship.
-
C.
mainConflict
Indicates the primary opposing force, problem, or struggle that drives tension and narrative progression between entities or sides.
-
D.
hasOngoingConflict
Indicates that there is a current, unresolved state of opposition, dispute, or hostilities between the related entities.
-
E.
hasConflictSide
Indicates that an entity participates as a specific side or party in a conflict or dispute.
- 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_69f76ea5f5588190bd0b28c82e975640 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.