Triple
T37538920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nagrand |
E933276
|
entity |
| Predicate | notableQuestline |
P183780
|
FINISHED |
| Object | Ring of Blood arena 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: Ring of Blood arena quests | Statement: [Nagrand, notableQuestline, Ring of Blood arena quests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableQuestline Context triple: [Nagrand, notableQuestline, Ring of Blood arena quests]
-
A.
notableAdventure
Indicates that an entity is recognized for having undertaken or been involved in a particularly significant or memorable adventure.
-
B.
questlineName
Indicates the specific title or identifier assigned to a questline within a larger sequence of related quests or missions.
-
C.
isLegendaryQuest
Indicates that a quest is of legendary status, typically denoting exceptional difficulty, rarity, or importance within its context.
-
D.
questlineFeature
chosen
Indicates that something is a notable element, step, or component within a larger questline or narrative progression.
-
E.
notableStoryArc
Indicates that there exists a significant or prominent narrative storyline or plot development involving the subject.
- 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_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.