Triple
T38585227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patch 2.1 – Black Temple |
E932330
|
entity |
| Predicate | addedLore |
P99630
|
FINISHED |
| Object | Illidan Stormrage storyline expansion |
—
|
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: Illidan Stormrage storyline expansion | Statement: [Patch 2.1 – Black Temple, addedLore, Illidan Stormrage storyline expansion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addedLore Context triple: [Patch 2.1 – Black Temple, addedLore, Illidan Stormrage storyline expansion]
-
A.
materialInLore
Indicates that a material is referenced, described, or plays a role within a body of lore or fictional/worldbuilding context.
-
B.
hasLoreContext
chosen
Indicates that something is associated with or situated within a particular narrative, historical, or fictional background or storyline.
-
C.
laterAdditionsBy
Indicates that one entity consists of or represents additions or modifications that were made to another entity at a later time.
-
D.
reputationInLore
Indicates how an entity is regarded or reputed within a fictional or narrative lore context.
-
E.
addedFor
Indicates that one entity was created, included, or introduced specifically for the benefit, use, or purpose of 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.