Triple
T37509761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Angrathar the Wrathgate |
E932185
|
entity |
| Predicate | isPartOfQuestline |
P183780
|
FINISHED |
| Object | Wrathgate quest chain |
—
|
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: Wrathgate quest chain | Statement: [Battle of Angrathar the Wrathgate, isPartOfQuestline, Wrathgate quest chain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfQuestline Context triple: [Battle of Angrathar the Wrathgate, isPartOfQuestline, Wrathgate quest chain]
-
A.
isLegendaryQuest
Indicates that a quest is of legendary status, typically denoting exceptional difficulty, rarity, or importance within its context.
-
B.
questlineAvailableIn
Indicates that a particular questline can be accessed or played within a specified game, mode, or context.
-
C.
questProgression
Indicates the ordered advancement of a quest through its defined stages or milestones.
-
D.
questlineName
Indicates the specific title or identifier assigned to a questline within a larger sequence of related quests or missions.
-
E.
questlineFeature
chosen
Indicates that something is a notable element, step, or component within a larger questline or narrative progression.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0010e46d948190a51111b5270fade7 |
completed | May 10, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_6a001061d34c8190bfe73f3d7c061eb7 |
completed | May 10, 2026, 4:58 a.m. |
Created at: May 3, 2026, 4:17 p.m.