Triple
T17172550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Society of Soul |
E416771
|
entity |
| Predicate | roleInDungeonFamily |
P126369
|
FINISHED |
| Object | in-house production collective |
—
|
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: in-house production collective | Statement: [Society of Soul, roleInDungeonFamily, in-house production collective]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInDungeonFamily Context triple: [Society of Soul, roleInDungeonFamily, in-house production collective]
-
A.
roleAtRagnarok
Indicates the specific function, position, or part an entity is expected to have or perform during Ragnarok.
-
B.
roleInShadowlands
Indicates that one entity has a specific function, position, or significance within the context of the Shadowlands.
-
C.
roleInDiablo
Indicates the specific function, position, or character type an entity has within the context of the Diablo game series.
-
D.
roleAtLarianStudios
Indicates that an entity holds or held a specific role or position at Larian Studios.
-
E.
roleInGameplay
Indicates the specific function or responsibility an entity has within the context of gameplay or game mechanics.
- F. None of above. chosen
Provenance (4 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3fc0ac22481909e992bb3a6ba36ad |
completed | April 18, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69e3873f62108190966c4e741ebd548d |
completed | April 18, 2026, 1:29 p.m. |
Created at: April 10, 2026, 5:37 a.m.