Triple

T2432338
Position Surface form Disambiguated ID Type / Status
Subject Vicarious Visions E52873 entity
Predicate roleInDiabloIIResurrected P39168 FINISHED
Object lead development studio 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: lead development studio | Statement: [Vicarious Visions, roleInDiabloIIResurrected, lead development studio]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleInDiabloIIResurrected
Context triple: [Vicarious Visions, roleInDiabloIIResurrected, lead development studio]
  • A. roleInTheology
    Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
  • B. roleAtMidway
    Indicates that an entity holds or held a specific role, position, or function at the midpoint or intermediate stage of a process, event, or time period.
  • C. featuresCharacterRole
    Indicates that a work includes a character appearing in a specific narrative or functional role.
  • D. deFactoRole
    Indicates that an entity effectively functions in a role or capacity in practice, even if that role is not formally or officially assigned.
  • E. identificationRole
    Indicates that an entity serves as an identifier or plays a role in uniquely distinguishing or recognizing another entity.
  • 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_69ab4959bcc0819083246f9fb10439e3 completed March 6, 2026, 9:38 p.m.
NER Named-entity recognition batch_69abcc74a5108190a3a9631b0cc1a127 completed March 7, 2026, 6:57 a.m.
PD Predicate disambiguation batch_69abc5aa1b60819081b87f7985c6cff3 completed March 7, 2026, 6:28 a.m.
PDg Predicate description generation batch_69abcc73d2e48190b6ad5f3ee75b74eb completed March 7, 2026, 6:57 a.m.
Created at: March 6, 2026, 9:43 p.m.