Triple
T11927064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diablo III: Reaper of Souls |
E283809
|
entity |
| Predicate | altersSystem |
P32380
|
FINISHED |
| Object | loot system |
—
|
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: loot system | Statement: [Diablo III: Reaper of Souls, altersSystem, loot system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: altersSystem Context triple: [Diablo III: Reaper of Souls, altersSystem, loot system]
-
A.
interchangeSystem
Indicates a relationship where two or more systems are connected in such a way that they can exchange or transfer items, data, or services between them.
-
B.
laterModification
Indicates that one entity is a modification or revision that occurs after another in time.
-
C.
replacedSystemBasedOn
Indicates that one system was substituted for another specifically on the basis of certain criteria, conditions, or evaluations.
-
D.
system
Indicates that an entity functions as or belongs to a structured, organized set of components or processes that operate together as a system.
-
E.
associatedSystem
chosen
Indicates that one entity is functionally or contextually linked to a particular system with which it interacts or to which it belongs.
- 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_69d6ab2ce9c48190b5d39511b524f666 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e8e3ff308190851ce656286bc67e |
completed | April 10, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3af0188190bfb22be5c97b3349 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.