Triple
T32461111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rene Kirby |
E829573
|
entity |
| Predicate | usedRealLifeDisabilityInRole |
P101225
|
FINISHED |
| Object | Shallow Hal |
—
|
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: Shallow Hal | Statement: [Rene Kirby, usedRealLifeDisabilityInRole, Shallow Hal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedRealLifeDisabilityInRole Context triple: [Rene Kirby, usedRealLifeDisabilityInRole, Shallow Hal]
-
A.
hasDisabilityRepresentation
Indicates that something includes, portrays, or accounts for the presence and experiences of people with disabilities.
-
B.
fictionalDisability
Indicates that an entity has a disability that exists only in fictional or imaginary contexts, rather than in real-world medical or social classifications.
-
C.
causeOfDisability
Indicates that one entity is the reason or source that brings about another entity’s disability.
-
D.
disability
Indicates that an entity has a physical, mental, or sensory impairment that substantially limits one or more major life activities.
-
E.
portraysCharacterWithDisability
chosen
Indicates that an entity depicts or represents a character who has a disability.
- 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_69f3491df9288190afc0b23b1d6e72ce |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c3219a4481909ebcc338d4bd9e7a |
completed | May 3, 2026, 3:38 a.m. |
| PD | Predicate disambiguation | batch_69f6ba700a708190ab6db62791e43774 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:57 a.m.