Triple
T13569452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spellmonger |
E324118
|
entity |
| Predicate | primaryConflictType |
P1397
|
FINISHED |
| Object | large-scale 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: large-scale war | Statement: [Spellmonger, primaryConflictType, large-scale war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryConflictType Context triple: [Spellmonger, primaryConflictType, large-scale war]
-
A.
mainConflict
Indicates the primary opposing force, problem, or struggle that drives tension and narrative progression between entities or sides.
-
B.
conflictType
chosen
Indicates the specific kind or category of conflict that characterizes the relationship or interaction between entities.
-
C.
centralConflictIn
Indicates that one situation, issue, or opposition serves as the primary source of tension or struggle within another context, such as a story, event, or scenario.
-
D.
typicalConflict
Indicates that there is a commonly occurring or characteristic conflict or opposition between the related entities.
-
E.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular 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_69d8076830b48190910a902bae5888e2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb00f5b8881908617f42d227ed137 |
completed | April 12, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69dbae161a0481909f9d3f40ca4e0ac5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:48 p.m.