Triple
T11642177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World of Warcraft: Battle for Azeroth |
E276684
|
entity |
| Predicate | expansionFocus |
P31647
|
FINISHED |
| Object | faction 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: faction war | Statement: [World of Warcraft: Battle for Azeroth, expansionFocus, faction war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionFocus Context triple: [World of Warcraft: Battle for Azeroth, expansionFocus, faction war]
-
A.
expands
Indicates that one entity increases in size, volume, scope, or extent relative to a previous state or another entity.
-
B.
expandsIn
Indicates that one entity grows, spreads, or extends its presence or influence within the space, scope, or context defined by another entity.
-
C.
focusType
chosen
Indicates the specific kind or category of focus or attention that is being applied to or associated with an entity or interaction.
-
D.
expansionRegion
Indicates a region or area into which something (such as a structure, process, or influence) is intended or allowed to expand.
-
E.
focusesOn
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a260ab488190ab1c00d9850f3096 |
completed | April 10, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.