Triple
T38590157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackrock Mountain raid complex |
E932434
|
entity |
| Predicate | notableBossNearby |
P39585
|
FINISHED |
| Object | Emperor Thaurissan |
E2238338
|
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: Emperor Thaurissan | Statement: [Blackrock Mountain raid complex, notableBossNearby, Emperor Thaurissan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBossNearby Context triple: [Blackrock Mountain raid complex, notableBossNearby, Emperor Thaurissan]
-
A.
notableBoss
Indicates that one entity is a boss or superior of another in a way that is particularly prominent, distinguished, or noteworthy.
-
B.
hasNotableNearbyEntity
chosen
Indicates that one entity has another significant or noteworthy entity located in its close physical or contextual proximity.
-
C.
optionalBoss
Indicates that one entity may serve as a boss or supervisor of another, but this relationship is not required or always present.
-
D.
hasBossLocation
Indicates that an entity’s boss is located at a particular place or position.
-
E.
requiresBossFight
Indicates that completing or progressing past a certain point necessitates defeating a designated boss character in combat.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a42158362248190aa60d7501b164af2 |
completed | June 29, 2026, 6:49 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.