Triple
T37512204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scosglen |
E932543
|
entity |
| Predicate | primaryRoleInGame |
P134117
|
FINISHED |
| Object | major explorable zone in Diablo IV |
—
|
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: major explorable zone in Diablo IV | Statement: [Scosglen, primaryRoleInGame, major explorable zone in Diablo IV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRoleInGame Context triple: [Scosglen, primaryRoleInGame, major explorable zone in Diablo IV]
-
A.
roleInGameplay
Indicates the specific function or responsibility an entity has within the context of gameplay or game mechanics.
-
B.
associatedPlayerRole
Indicates a relationship where a specific role or function is linked to, or held by, a particular player.
-
C.
primaryRoleFor
Indicates that one entity serves as the main or most important role or function for another entity.
-
D.
roleInDiceGame
Indicates the specific function or position an entity holds within the context of a dice game (e.g., shooter, dealer, scorer).
-
E.
principalRoleIn
chosen
Indicates that an entity holds the primary or leading role in a particular context, activity, or relationship.
- 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_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.