Triple
T38644502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rise of Azshara |
E938680
|
entity |
| Predicate | expandsStoryline |
P84989
|
FINISHED |
| Object | Naga and Azshara narrative |
—
|
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: Naga and Azshara narrative | Statement: [Rise of Azshara, expandsStoryline, Naga and Azshara narrative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expandsStoryline Context triple: [Rise of Azshara, expandsStoryline, Naga and Azshara narrative]
-
A.
expandsBackstoryOf
Indicates that one entity provides additional background details or context that elaborate on the history or origins of another entity.
-
B.
storyline
Indicates that one entity serves as the narrative plot or sequence of events associated with another entity.
-
C.
hasExpandedNarrativesIn
chosen
Indicates that something has developed or introduced more detailed, diverse, or extensive narratives within a specified context or medium.
-
D.
storylineEvent
Indicates that one event occurs as a distinct step or component within a larger narrative or storyline.
-
E.
storylinesInclude
Indicates that certain storylines are contained within, or form part of, a larger narrative or collection of narratives.
- 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_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
Created at: May 3, 2026, 4:32 p.m.