Triple
T37541702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World of Warcraft patch 9.0.1 |
E933339
|
entity |
| Predicate | associatedExpansion |
P201864
|
FINISHED |
| Object | Shadowlands |
E273800
|
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: Shadowlands | Statement: [World of Warcraft patch 9.0.1, associatedExpansion, Shadowlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedExpansion Context triple: [World of Warcraft patch 9.0.1, associatedExpansion, Shadowlands]
-
A.
expansionLinkedTo
Indicates that one entity’s growth, increase, or enlargement is causally or logically connected to the expansion of another entity.
-
B.
belongsToExpansion
chosen
Indicates that something is a component or member of a larger expansion set, collection, or release.
-
C.
associatedFort
Indicates that one entity is connected or linked to a particular fort, typically as its related or corresponding fortification.
-
D.
associatedThrough
Indicates that two entities are connected or related to each other by means of a specified intermediary, context, or linkage.
-
E.
supportedExpansionOf
Indicates that one entity actively aided, endorsed, or facilitated the growth, extension, or enlargement of another entity or domain.
- 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_69f76ec999288190ae26ec7b6aea7046 |
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_6a4117d6a63c8190aa2881befb8db485 |
completed | June 28, 2026, 12:47 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.