Triple
T35830701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deadwind Pass |
E1035788
|
entity |
| Predicate | hasDungeonEntrance |
P6140
|
FINISHED |
| Object | Karazhan raid |
—
|
NE NERFINISHED |
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: Karazhan raid | Statement: [Deadwind Pass, hasDungeonEntrance, Karazhan raid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDungeonEntrance Context triple: [Deadwind Pass, hasDungeonEntrance, Karazhan raid]
-
A.
hasDungeon
Indicates that one entity possesses, contains, or includes a dungeon as part of its structure, property, or domain.
-
B.
hasEntrance
chosen
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
-
C.
hasEntranceOn
Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of another entity.
-
D.
hasCaveEntranceDepth
Indicates the depth or vertical distance of a cave’s entrance relative to a reference level (such as ground surface or sea level).
-
E.
hasEntranceGimmick
Indicates that an entity features a distinctive or notable gimmick, stunt, or special element associated with its entrance or initial appearance.
- 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_69f76e192a94819082db360cb91e6a8d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.