Triple
T37509115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lords of Dread |
E932171
|
entity |
| Predicate | isPatchContentOf |
P22683
|
FINISHED |
| Object | Patch 9.2 Eternity's End |
—
|
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: Patch 9.2 Eternity's End | Statement: [Lords of Dread, isPatchContentOf, Patch 9.2 Eternity's End]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPatchContentOf Context triple: [Lords of Dread, isPatchContentOf, Patch 9.2 Eternity's End]
-
A.
isModifiedAs
Indicates that an entity has been altered or changed from its original state in some specified manner.
-
B.
hasContentFrom
chosen
Indicates that one entity’s content is derived from, includes, or is based on another entity.
-
C.
isUpdateFor
Indicates that one entity serves as a newer or modified version that replaces or revises another entity.
-
D.
containsDelta
Indicates that one entity includes or encompasses a change, difference, or delta associated with another entity.
-
E.
formsDeltaWith
Indicates that one entity combines or interacts with another to produce a change or difference (a “delta”) between states, values, or conditions.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.