Triple
T36962747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Regent Hiram Burrows |
E914348
|
entity |
| Predicate | appearsAsNPCIn |
P119053
|
FINISHED |
| Object | Dishonored |
—
|
NE NERFINISHED |
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: Dishonored | Statement: [Lord Regent Hiram Burrows, appearsAsNPCIn, Dishonored]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsAsNPCIn Context triple: [Lord Regent Hiram Burrows, appearsAsNPCIn, Dishonored]
-
A.
appearsWithCharacter
Indicates that two characters are shown or present together within the same scene, shot, or context.
-
B.
appearsAsNPCGroup
chosen
Indicates that the subject is presented or functions as a non-player-character (NPC) group within a game or interactive environment.
-
C.
appearsAgainst
Indicates that one entity is visually or publicly presented in opposition to, or in contrast with, another entity.
-
D.
appearsInFictionAs
Indicates that one entity is depicted or represented as a character, figure, or element within a fictional work or narrative.
-
E.
appearsIn
Indicates that an entity is present, featured, or occurs within a particular context, work, or medium.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe9fb9735c8190a360b556c9d00b3f |
completed | May 9, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69fe9eaa88008190a9b2a469dc685002 |
completed | May 9, 2026, 2:40 a.m. |
Created at: May 3, 2026, 4:14 p.m.