Triple
T38583837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terokkar Forest |
E932301
|
entity |
| Predicate | containsDungeonHub |
P100053
|
FINISHED |
| Object | Auchindoun |
E2234705
|
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: Auchindoun | Statement: [Terokkar Forest, containsDungeonHub, Auchindoun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsDungeonHub Context triple: [Terokkar Forest, containsDungeonHub, Auchindoun]
-
A.
isInDungeonHub
Indicates that an entity is currently located within, or associated with, the Dungeon Hub area or environment.
-
B.
hasDungeon
chosen
Indicates that one entity possesses, contains, or includes a dungeon as part of its structure, property, or domain.
-
C.
requiresDungeon
Indicates that performing the action or establishing the relationship is contingent on the presence or completion of a specific dungeon.
-
D.
hasQuestHubIn
Indicates that a quest hub is located within or associated with a particular place or region.
-
E.
isInCavernSystem
Indicates that one entity is located within or forms part of an interconnected network of underground caverns associated with another entity.
- 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_6a023f290e3081909a465d6cfb79518a |
completed | May 11, 2026, 8:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a42158362248190aa60d7501b164af2 |
completed | June 29, 2026, 6:49 a.m. |
| PD | Predicate disambiguation | batch_6a0238d1436c8190ab0251030b01902e |
completed | May 11, 2026, 8:15 p.m. |
Created at: May 3, 2026, 4:32 p.m.