Triple
T35830683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deadwind Pass |
E1035788
|
entity |
| Predicate | expansionIntroduced |
P100003
|
FINISHED |
| Object | World of Warcraft (classic) |
—
|
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 (classic) | Statement: [Deadwind Pass, expansionIntroduced, World of Warcraft (classic)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionIntroduced Context triple: [Deadwind Pass, expansionIntroduced, World of Warcraft (classic)]
-
A.
expansionAdded
Indicates that an additional component, feature, or content has been incorporated into an existing entity or system.
-
B.
introduced
Indicates that one entity caused another entity to become known, presented, or brought into use for the first time to a person, group, or context.
-
C.
introducedInExpansion
chosen
Indicates that something (such as a feature, item, or concept) was first added or made available as part of a specific expansion.
-
D.
expands
Indicates that one entity increases in size, volume, scope, or extent relative to a previous state or another entity.
-
E.
expansionType
Indicates the specific manner or category by which something grows, extends, or increases in scope or size.
- 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_69f76e192a94819082db360cb91e6a8d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.