Triple
T33954872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Den enfaldige mördaren |
E870540
|
entity |
| Predicate | hasProtagonistDisability |
P101225
|
FINISHED |
| Object | speech impairment |
—
|
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: speech impairment | Statement: [Den enfaldige mördaren, hasProtagonistDisability, speech impairment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProtagonistDisability Context triple: [Den enfaldige mördaren, hasProtagonistDisability, speech impairment]
-
A.
portraysCharacterWithDisability
chosen
Indicates that an entity depicts or represents a character who has a disability.
-
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.
hasDisabilityRepresentation
Indicates that something includes, portrays, or accounts for the presence and experiences of people with disabilities.
-
D.
hasProtagonistAbility
Indicates that a protagonist possesses a specific ability, power, or special skill.
-
E.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
- 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_69f3499c2d7481909c953a5010227725 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a020ab9630c8190a55efd5704cc6043 |
completed | May 11, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_6a020800e2b88190a1a37e710d8c92bf |
completed | May 11, 2026, 4:46 p.m. |
Created at: May 1, 2026, 1:49 a.m.