Triple
T37539166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serpentshrine Cavern |
E933281
|
entity |
| Predicate | attunementQuestline |
P184431
|
FINISHED |
| Object | The Vials of Eternity |
—
|
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: The Vials of Eternity | Statement: [Serpentshrine Cavern, attunementQuestline, The Vials of Eternity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attunementQuestline Context triple: [Serpentshrine Cavern, attunementQuestline, The Vials of Eternity]
-
A.
requiresAttunementOriginal
Indicates that the item or effect necessitates attunement by a creature before its full properties or benefits can be used.
-
B.
centralQuest
Indicates that an action, objective, or storyline serves as the primary or main quest within a larger narrative or mission structure.
-
C.
questlineFeature
Indicates that something is a notable element, step, or component within a larger questline or narrative progression.
-
D.
questContent
Indicates that one entity is the content, objective, or narrative substance of a quest associated with another entity.
-
E.
questlineName
chosen
Indicates the specific title or identifier assigned to a questline within a larger sequence of related quests or missions.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.