Triple
T37551633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forge of Souls |
E933602
|
entity |
| Predicate | isInDungeonHub |
P188265
|
FINISHED |
| Object | Icecrown Citadel 5-player wings |
—
|
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: Icecrown Citadel 5-player wings | Statement: [Forge of Souls, isInDungeonHub, Icecrown Citadel 5-player wings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInDungeonHub Context triple: [Forge of Souls, isInDungeonHub, Icecrown Citadel 5-player wings]
-
A.
isInCavernSystem
Indicates that one entity is located within or forms part of an interconnected network of underground caverns associated with another entity.
-
B.
hasDungeon
Indicates that one entity possesses, contains, or includes a dungeon as part of its structure, property, or domain.
-
C.
isInTunnelSystem
Indicates that one entity is located within or forms part of a tunnel system associated with another entity.
-
D.
isNearEntrance
Indicates that an entity is located close to the entrance of a place or structure.
-
E.
hasQuestHubIn
Indicates that a quest hub is located within or associated with a particular place or region.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba5ee00fc81909be7b947a3f95034 |
completed | May 6, 2026, 8:34 p.m. |
Created at: May 3, 2026, 4:17 p.m.