Triple
T38584789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shadow Labyrinth |
E932321
|
entity |
| Predicate | partOfDungeonHub |
P188265
|
FINISHED |
| Object | Auchindoun dungeon hub |
—
|
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: Auchindoun dungeon hub | Statement: [Shadow Labyrinth, partOfDungeonHub, Auchindoun dungeon hub]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfDungeonHub Context triple: [Shadow Labyrinth, partOfDungeonHub, Auchindoun dungeon hub]
-
A.
hasDungeon
Indicates that one entity possesses, contains, or includes a dungeon as part of its structure, property, or domain.
-
B.
isInDungeonHub
chosen
Indicates that an entity is currently located within, or associated with, the Dungeon Hub area or environment.
-
C.
majorDungeonFeature
Indicates that something serves as a primary or defining structural or thematic element of a dungeon.
-
D.
dungeonType
Indicates the specific category or kind of dungeon associated with an entity or location.
-
E.
hallDescription
Indicates a descriptive relationship that specifies the characteristics or details of a hall.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a01e27bb77c8190a7686b77a524f177 |
completed | May 11, 2026, 2:06 p.m. |
| PD | Predicate disambiguation | batch_6a01da2614788190b31db15539f5ba58 |
completed | May 11, 2026, 1:31 p.m. |
Created at: May 3, 2026, 4:32 p.m.