Triple
T38583774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hellfire Peninsula |
E932300
|
entity |
| Predicate | containsRaidEntrance |
P191474
|
FINISHED |
| Object | Magtheridon’s Lair |
E933280
|
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: Magtheridon’s Lair | Statement: [Hellfire Peninsula, containsRaidEntrance, Magtheridon’s Lair]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsRaidEntrance Context triple: [Hellfire Peninsula, containsRaidEntrance, Magtheridon’s Lair]
-
A.
hasEntrancesIn
Indicates that an entity has one or more entrances located within or opening into another specified entity or area.
-
B.
raidEntranceLocation
chosen
Indicates the location where a raid begins or where raiders enter a target area.
-
C.
hasHiddenEntrance
Indicates that an entity possesses a concealed or non-obvious entrance or access point.
-
D.
hasEntranceOn
Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of another entity.
-
E.
hasEntrance
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
- 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_6a0238010fa481909b07a5c22aa0abde |
completed | May 11, 2026, 8:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a423f6f7e7c8190a655f8c77107d82a |
completed | June 29, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_6a0236cfdcb481908323b67b925c76d9 |
completed | May 11, 2026, 8:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.