Triple
T35830707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deadwind Pass |
E1035788
|
entity |
| Predicate | questContent |
P184907
|
FINISHED |
| Object | stories about Medivh and Karazhan |
—
|
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: stories about Medivh and Karazhan | Statement: [Deadwind Pass, questContent, stories about Medivh and Karazhan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: questContent Context triple: [Deadwind Pass, questContent, stories about Medivh and Karazhan]
-
A.
questType
Indicates the specific category or nature of a quest that characterizes what kind of mission or objective it represents.
-
B.
questName
Indicates the specific title or identifier assigned to a quest within a game or narrative system.
-
C.
questGiverIn
Indicates that an entity serves as the quest giver within a specified quest, location, or context.
-
D.
questlineFeature
Indicates that something is a notable element, step, or component within a larger questline or narrative progression.
-
E.
questlineName
Indicates the specific title or identifier assigned to a questline within a larger sequence of related quests or missions.
- 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_69f76e192a94819082db360cb91e6a8d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b628b17c8190aa058c1a51852a27 |
completed | May 3, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b5cadd308190a864245a21b08f9a |
completed | May 3, 2026, 8:53 p.m. |
Created at: May 3, 2026, 4:06 p.m.