Triple
T37515544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delirium |
E932623
|
entity |
| Predicate | hasEndgameContent |
P100073
|
FINISHED |
| Object | Simulacrum waves of monsters |
—
|
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: Simulacrum waves of monsters | Statement: [Delirium, hasEndgameContent, Simulacrum waves of monsters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEndgameContent Context triple: [Delirium, hasEndgameContent, Simulacrum waves of monsters]
-
A.
hasGameContent
Indicates that an entity includes, provides, or is associated with game-related material or features.
-
B.
hasGameEndCondition
Indicates that an entity specifies the condition or set of conditions under which a game is considered finished or concluded.
-
C.
endgameContentFor
chosen
Indicates that something serves as endgame content designed for a particular game, mode, or player progression stage.
-
D.
hasUnfinishedEnding
Indicates that an entity concludes in an incomplete, unresolved, or open-ended manner rather than reaching a fully finished state.
-
E.
hasInGameActivities
Indicates that an entity includes or offers specific activities or actions that can be performed within a game context.
- 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_69fe0d165a48819098b854318a50d76c |
completed | May 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69fe0931002481908a95b34f95e9f64e |
completed | May 8, 2026, 4:02 p.m. |
Created at: May 3, 2026, 4:17 p.m.