Triple
T2326828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conrad Veidt |
E48305
|
entity |
| Predicate | portrayedRolesType |
P36975
|
FINISHED |
| Object | villainous characters |
—
|
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: villainous characters | Statement: [Conrad Veidt, portrayedRolesType, villainous characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portrayedRolesType Context triple: [Conrad Veidt, portrayedRolesType, villainous characters]
-
A.
portrayedByAlsoPlays
Indicates that the actor who portrays a given character also plays another specified role or character.
-
B.
playedRoleIn
Indicates that an entity performed or assumed a specific role or character within a particular event, production, or context.
-
C.
portrayedByWork
Indicates that a work (such as a film, book, or artwork) depicts, represents, or portrays a particular entity.
-
D.
hasPlayedRole
chosen
Indicates that an entity has performed or portrayed a particular role or character in some context (such as a film, play, or production).
-
E.
portrayedBy
Indicates that one entity serves as the actor or performer who represents or plays the role of another entity in a 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_69a88aa308a88190b0b86c011fda7fce |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abcc30c5e881908c5d526d7e7491d0 |
completed | March 7, 2026, 6:56 a.m. |
| PD | Predicate disambiguation | batch_69abc5926d048190a535e3f23d41de2a |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:50 p.m.