Triple
T38585203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patch 2.1 – Black Temple |
E932330
|
entity |
| Predicate | introducedQuestHub |
P199222
|
FINISHED |
| Object | Ogri'la |
—
|
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: Ogri'la | Statement: [Patch 2.1 – Black Temple, introducedQuestHub, Ogri'la]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedQuestHub Context triple: [Patch 2.1 – Black Temple, introducedQuestHub, Ogri'la]
-
A.
hasQuestHubIn
Indicates that a quest hub is located within or associated with a particular place or region.
-
B.
centralQuest
Indicates that an action, objective, or storyline serves as the primary or main quest within a larger narrative or mission structure.
-
C.
questHubNPC
Indicates that an NPC serves as a central provider or coordinator of quests for players.
-
D.
addsQuest
Indicates that one entity assigns or introduces a quest to another entity or into a system.
-
E.
zoneQuestHub
Indicates a relationship where a particular zone serves as the central hub or main base for quests within a game or system.
- F. None of above. chosen
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_69ff2636e2bc8190bba91eff91431c6e |
completed | May 9, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69ff25c65be48190868480d94e1c4e89 |
completed | May 9, 2026, 12:17 p.m. |
| PDg | Predicate description generation | batch_69ff263632608190a99beb73608066d8 |
completed | May 9, 2026, 12:19 p.m. |
Created at: May 3, 2026, 4:32 p.m.