Triple
T38584831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Black Morass |
E932322
|
entity |
| Predicate | requiresQuest |
P192033
|
FINISHED |
| Object | The Opening of the Dark Portal |
—
|
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 Opening of the Dark Portal | Statement: [The Black Morass, requiresQuest, The Opening of the Dark Portal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresQuest Context triple: [The Black Morass, requiresQuest, The Opening of the Dark Portal]
-
A.
unlockRequiresQuest
chosen
Indicates that gaining access to something is conditional on completing a specific quest.
-
B.
questRequirementCount
Indicates the number of required elements, tasks, or conditions that must be fulfilled for a quest.
-
C.
requiresSkill
Indicates that performing or engaging in one entity (e.g., a task or role) depends on possessing or applying a specific skill represented by the other entity.
-
D.
isLegendaryQuest
Indicates that a quest is of legendary status, typically denoting exceptional difficulty, rarity, or importance within its context.
-
E.
questType
Indicates the specific category or nature of a quest that characterizes what kind of mission or objective it represents.
- 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_6a00bb3a6f888190b3ecd0fbc9af9b4a |
completed | May 10, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_6a00b902dbf881909e098ff102b7ea7e |
completed | May 10, 2026, 4:57 p.m. |
Created at: May 3, 2026, 4:32 p.m.