Triple
T37462076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yogg-Saron Spell Mage |
E930941
|
entity |
| Predicate | originExpansion |
P113385
|
FINISHED |
| Object | Whispers of the Old Gods |
E273753
|
NE 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: Whispers of the Old Gods | Statement: [Yogg-Saron Spell Mage, originExpansion, Whispers of the Old Gods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originExpansion Context triple: [Yogg-Saron Spell Mage, originExpansion, Whispers of the Old Gods]
-
A.
expansionFrom
chosen
Indicates that one entity results from or is derived through the enlargement, extension, or unfolding of another entity.
-
B.
expansionLocation
Indicates the place or area where something grows, spreads, or extends its presence or influence.
-
C.
originalExpansionClass
Indicates that one entity is the original or source class from which another entity has been expanded, derived, or extended.
-
D.
expands
Indicates that one entity increases in size, volume, scope, or extent relative to a previous state or another entity.
-
E.
expansionAdded
Indicates that an additional component, feature, or content has been incorporated into an existing entity or system.
- F. None of above.
Provenance (4 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a43011fa5b0819080146bf94c3d4ee4 |
completed | June 29, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.