Triple
T37455935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashes of Malmouth |
E930798
|
entity |
| Predicate | expandsEndgame |
P100073
|
FINISHED |
| Object | Grim Dawn |
—
|
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: Grim Dawn | Statement: [Ashes of Malmouth, expandsEndgame, Grim Dawn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expandsEndgame Context triple: [Ashes of Malmouth, expandsEndgame, Grim Dawn]
-
A.
endgameContentFor
chosen
Indicates that something serves as endgame content designed for a particular game, mode, or player progression stage.
-
B.
endgameIntegration
Indicates that one entity is incorporated into or aligned with another as part of a final or ultimate phase of a process, strategy, or sequence.
-
C.
endgameItemIn
Indicates that a particular item is present or available within the endgame phase or endgame-specific context.
-
D.
endedPlay
Indicates that an entity has brought a play, performance, or game to a conclusion.
-
E.
ElamEnding
Indicates that an entity marks the end or termination of something related to Elam (e.g., an Elam-related period, event, or process).
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:17 p.m.