Triple
T38644785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | War of the Thorns |
E938686
|
entity |
| Predicate | expansionAssociatedWith |
P76627
|
FINISHED |
| Object | Battle for Azeroth |
—
|
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: Battle for Azeroth | Statement: [War of the Thorns, expansionAssociatedWith, Battle for Azeroth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionAssociatedWith Context triple: [War of the Thorns, expansionAssociatedWith, Battle for Azeroth]
-
A.
expansionLinkedTo
chosen
Indicates that one entity’s growth, increase, or enlargement is causally or logically connected to the expansion of another entity.
-
B.
expands
Indicates that one entity increases in size, volume, scope, or extent relative to a previous state or another entity.
-
C.
expansionType
Indicates the specific manner or category by which something grows, extends, or increases in scope or size.
-
D.
expansionAlongside
Indicates that one entity expands or grows in parallel with, and in relation to, the expansion of another entity.
-
E.
expansionRelevance
Indicates how pertinent or significant a given expansion (such as an extension, elaboration, or added content) is to the original item or context.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
Created at: May 3, 2026, 4:32 p.m.