Triple
T37552372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Nighthold |
E933616
|
entity |
| Predicate | factionConflict |
P192018
|
FINISHED |
| Object | Horde |
—
|
NE NERFINISHED |
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: Horde | Statement: [The Nighthold, factionConflict, Horde]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: factionConflict Context triple: [The Nighthold, factionConflict, Horde]
-
A.
loreConflict
Indicates that there is an inconsistency, contradiction, or incompatibility between pieces of lore or canonical information.
-
B.
factionContested
chosen
Indicates that a faction is actively challenging, disputing, or competing for control or influence over a particular entity, area, or interest.
-
C.
politicalConflict
Indicates a relationship where entities are engaged in opposing political positions, struggles, or disputes, often involving competition for power, influence, or policy outcomes.
-
D.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
E.
conflictGround
Indicates that one entity is the cause, basis, or subject matter of a conflict involving another entity.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: May 3, 2026, 4:17 p.m.