Triple

T36962388
Position Surface form Disambiguated ID Type / Status
Subject Gristol E914340 entity
Predicate hasNotableCharacterAssociated P97477 FINISHED
Object Hiram Burrows
Hiram Burrows is the ruthless Lord Regent of Gristol in the Dishonored video game series, known for orchestrating a coup and ruling with authoritarian control.
E2273477 NE 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: Hiram Burrows | Statement: [Gristol, hasNotableCharacterAssociated, Hiram Burrows]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Hiram Burrows
Triple: [Gristol, hasNotableCharacterAssociated, Hiram Burrows]
Generated description
Hiram Burrows is the ruthless Lord Regent of Gristol in the Dishonored video game series, known for orchestrating a coup and ruling with authoritarian control.

Provenance (5 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_69f76e8c498c8190b2842db80aea8b3b completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69f9ff0e1538819090ce6a3f66cf1b26 completed May 5, 2026, 2:30 p.m.
NED1 Entity disambiguation (via context triple) batch_6a41d631c2548190a021564b99378840 completed June 29, 2026, 2:19 a.m.
NEDg Description generation batch_6a41da547e2481909ccd8b5698a5f78e completed June 29, 2026, 2:37 a.m.
NED2 Entity disambiguation (via description) batch_6a41daa4a87c8190b998dadf04640b7c completed June 29, 2026, 2:38 a.m.
Created at: May 3, 2026, 4:14 p.m.