Triple
T37512403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inarius |
E932547
|
entity |
| Predicate | firstIntroducedInLore |
P197695
|
FINISHED |
| Object | Diablo series backstory |
—
|
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: Diablo series backstory | Statement: [Inarius, firstIntroducedInLore, Diablo series backstory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstIntroducedInLore Context triple: [Inarius, firstIntroducedInLore, Diablo series backstory]
-
A.
introducedInGameAs
Indicates that an entity first appeared or was made available within a specific game title.
-
B.
areIntroducedBy
Indicates that one entity becomes known or presented to another entity through the action or mediation of a third party or process.
-
C.
firstAppearanceInLegendarium
chosen
Indicates the work or source within a fictional legendarium in which an entity is introduced or mentioned for the first time.
-
D.
firstUsedInGame
Indicates the game in which something (such as an item, mechanic, or concept) was first introduced or appeared.
-
E.
firstAppearedAt
Indicates the point in time or specific event at which an entity was first introduced, observed, or became known.
- 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.