Triple
T37513493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Search for Cain |
E932572
|
entity |
| Predicate | questOrder |
P189399
|
FINISHED |
| Object | third quest in Act I of Diablo II |
—
|
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: third quest in Act I of Diablo II | Statement: [The Search for Cain, questOrder, third quest in Act I of Diablo II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: questOrder Context triple: [The Search for Cain, questOrder, third quest in Act I of Diablo II]
-
A.
questGiverIn
Indicates that an entity serves as the quest giver within a specified quest, location, or context.
-
B.
questOrderedBy
Indicates that one entity is a quest that has been requested, assigned, or commissioned by another entity.
-
C.
questProgression
chosen
Indicates the ordered advancement of a quest through its defined stages or milestones.
-
D.
questContent
Indicates that one entity is the content, objective, or narrative substance of a quest associated with another entity.
-
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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:17 p.m.