Triple
T1800883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klaus Heissler |
E39714
|
entity |
| Predicate | genreRole |
P32515
|
FINISHED |
| Object | comedic supporting character |
—
|
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: comedic supporting character | Statement: [Klaus Heissler, genreRole, comedic supporting character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genreRole Context triple: [Klaus Heissler, genreRole, comedic supporting character]
-
A.
creativeRole
Indicates that an entity holds a specific creative function or responsibility in relation to another entity, such as a work or project.
-
B.
musicalRole
Indicates the specific function or part an entity performs within a musical context, such as in a performance, composition, or ensemble.
-
C.
actingRoleType
Indicates the specific type or category of role an entity performs when acting in a particular capacity or function.
-
D.
literaryRole
Indicates the specific narrative or functional role an entity holds within a literary work or text.
-
E.
featuresCharacterRole
Indicates that a work includes a character appearing in a specific narrative or functional role.
- 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_69a88632aa588190ba3978fde0db5bbd |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69aba67721788190951beae25e885457 |
completed | March 7, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69aa61d514c081908197ac1f7c7d7a88 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69aba67554788190b429f2b9f0a70310 |
completed | March 7, 2026, 4:15 a.m. |
Created at: March 4, 2026, 7:32 p.m.