Triple
T38585207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patch 2.1 – Black Temple |
E932330
|
entity |
| Predicate | introducedDailyQuests |
P71495
|
FINISHED |
| Object | Ogri'la daily quests |
—
|
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: Ogri'la daily quests | Statement: [Patch 2.1 – Black Temple, introducedDailyQuests, Ogri'la daily quests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedDailyQuests Context triple: [Patch 2.1 – Black Temple, introducedDailyQuests, Ogri'la daily quests]
-
A.
introducedQuestHub
Indicates that an entity has presented or made a quest hub available to another entity or group.
-
B.
hasDailyEvent
chosen
Indicates that an entity is associated with an event that occurs every day.
-
C.
addsQuest
Indicates that one entity assigns or introduces a quest to another entity or into a system.
-
D.
centralQuest
Indicates that an action, objective, or storyline serves as the primary or main quest within a larger narrative or mission structure.
-
E.
introducedContests
Indicates that an entity initiated or brought into existence one or more contests or competitive events.
- 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_69ff289541e0819096eeceb8e6332650 |
completed | May 9, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69ff281ab1988190920f0443be9f10cc |
completed | May 9, 2026, 12:27 p.m. |
Created at: May 3, 2026, 4:32 p.m.