Triple
T37550966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Death Knight |
E933588
|
entity |
| Predicate | startingExpansion |
P100003
|
FINISHED |
| Object | Wrath of the Lich King |
—
|
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: Wrath of the Lich King | Statement: [Death Knight, startingExpansion, Wrath of the Lich King]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startingExpansion Context triple: [Death Knight, startingExpansion, Wrath of the Lich King]
-
A.
introducedExpansion
Indicates that an entity caused a new expansion, extension, or enlargement of something to be brought into existence or put into use.
-
B.
introducedInExpansion
chosen
Indicates that something (such as a feature, item, or concept) was first added or made available as part of a specific expansion.
-
C.
hasExpansionSetNumber
Indicates that an entity is associated with a specific numbered position or identifier within an expansion set.
-
D.
startWithExpansion
Indicates that an action, process, or sequence begins with an initial phase of growth, enlargement, or increase before proceeding to subsequent stages.
-
E.
settingExpansion
Indicates that one setting or configuration broadens, extends, or adds to the scope or detail of another setting.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0124a5d7848190a6b56d18db2f661d |
completed | May 11, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_6a01243da1808190ada3ce553e3f55b6 |
completed | May 11, 2026, 12:35 a.m. |
Created at: May 3, 2026, 4:17 p.m.