Triple
T11547691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanctum of Domination |
E273811
|
entity |
| Predicate | notableEncounter |
P61643
|
FINISHED |
| Object | Sylvanas Windrunner multi-phase fight |
—
|
LITERAL 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: Sylvanas Windrunner multi-phase fight | Statement: [Sanctum of Domination, notableEncounter, Sylvanas Windrunner multi-phase fight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEncounter Context triple: [Sanctum of Domination, notableEncounter, Sylvanas Windrunner multi-phase fight]
-
A.
notableEncounterWith
chosen
Indicates that an entity has had a significant or noteworthy meeting, interaction, or confrontation with another entity.
-
B.
notableBoss
Indicates that one entity is a boss or superior of another in a way that is particularly prominent, distinguished, or noteworthy.
-
C.
hasNotableTribeAtEncounter
Indicates that, at the time of the encounter, the entity was associated with or identified as belonging to a notable tribe.
-
D.
notableAttack
Indicates that an entity carried out, was involved in, or is strongly associated with a particularly significant or well-known attack.
-
E.
notableScene
Indicates that a particular scene is especially significant, memorable, or noteworthy within a work or context.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e3ad548190b2c88332f5d919bd |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d8087cbe7c819085680f3d67ccc978 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.