Triple
T37471843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hibernal Hollow |
E931171
|
entity |
| Predicate | expansionSet |
P98691
|
FINISHED |
| Object | World of Warcraft: Shadowlands |
—
|
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: World of Warcraft: Shadowlands | Statement: [Hibernal Hollow, expansionSet, World of Warcraft: Shadowlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionSet Context triple: [Hibernal Hollow, expansionSet, World of Warcraft: Shadowlands]
-
A.
expansionSetting
Indicates the configuration or parameters that determine how something is expanded, extended, or unfolded in scope, size, or detail.
-
B.
expansionPack
chosen
Indicates that one item serves as an add-on or supplementary content package that extends the features or scope of another item.
-
C.
expansionSystem
Indicates a relationship where a system undergoes or enables expansion, typically by increasing its scope, capacity, or components over time.
-
D.
expansionAdded
Indicates that an additional component, feature, or content has been incorporated into an existing entity or system.
-
E.
expansionOptions
Indicates the available ways or configurations in which something can be extended, enlarged, or further developed.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: May 3, 2026, 4:17 p.m.