Triple
T38584152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karazhan |
E932307
|
entity |
| Predicate | Return to Karazhan instanceOf |
P193038
|
FINISHED |
| Object | mythic-only dungeon |
—
|
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: mythic-only dungeon | Statement: [Karazhan, Return to Karazhan instanceOf, mythic-only dungeon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Return to Karazhan instanceOf Context triple: [Karazhan, Return to Karazhan instanceOf, mythic-only dungeon]
-
A.
raidBossIn
Indicates that an entity serves as or is designated as the raid boss within a specified raid, instance, or location.
-
B.
bossEncounterStyle
Indicates how a boss is confronted or engaged during an encounter, such as the manner, format, or mechanics of the battle.
-
C.
mythicRaidSize
Indicates the number of participants involved when an activity or encounter is conducted at mythic difficulty.
-
D.
keyItemRaid
Indicates a raid or mission whose primary objective is to obtain or secure a key item.
-
E.
raidingPattern
Indicates a recurring or characteristic way in which raids are planned, organized, or carried out between entities.
- F. None of above. chosen
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_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
| PDg | Predicate description generation | batch_69fd35d029588190a525aa8a506e7708 |
completed | May 8, 2026, 1:01 a.m. |
Created at: May 3, 2026, 4:32 p.m.