Triple
T37461468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Huhuran |
E930926
|
entity |
| Predicate | bossLocation |
P119621
|
FINISHED |
| Object | Temple of Ahn'Qiraj (World of Warcraft) |
—
|
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: Temple of Ahn'Qiraj (World of Warcraft) | Statement: [Princess Huhuran, bossLocation, Temple of Ahn'Qiraj (World of Warcraft)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bossLocation Context triple: [Princess Huhuran, bossLocation, Temple of Ahn'Qiraj (World of Warcraft)]
-
A.
hasBossLocation
chosen
Indicates that an entity’s boss is located at a particular place or position.
-
B.
crewLocation
Indicates that a crew is located at, assigned to, or present in a specific place or environment.
-
C.
antagonistLocationFor
Indicates that a location serves as the primary place where an antagonist operates, resides, or exerts influence in relation to a given context or entity.
-
D.
notableGameLocation
Indicates that a particular place is recognized as a significant or prominent location within a game.
-
E.
questLocationFor
Indicates that a particular location is the place where a given quest occurs, is based, or must be undertaken.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.