Triple
T34250266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otello (1986 film) |
E878717
|
entity |
| Predicate | titleRolePerformedBy |
P42172
|
FINISHED |
| Object | Plácido Domingo |
—
|
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: Plácido Domingo | Statement: [Otello (1986 film), titleRolePerformedBy, Plácido Domingo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleRolePerformedBy Context triple: [Otello (1986 film), titleRolePerformedBy, Plácido Domingo]
-
A.
creditedRoleOf
Indicates that a particular role or position is formally acknowledged as being held or performed by a specific entity in a credit or attribution context.
-
B.
knownForRoleIn
Indicates that an entity is recognized or notable for performing a particular role in a specific work, project, or context.
-
C.
hasPortrayedPersonRole
Indicates that an entity has performed or held a specific role in portraying a particular person (e.g., in a film, play, or other representation).
-
D.
playsInRole
chosen
Indicates that an entity performs or appears in a specific role within a production, event, or context.
-
E.
namedPersonRole
Indicates that a person is identified by name as holding a specific role or position in a given context.
- 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_69f349b3618481909df955b063f305b2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff2eb19ad88190915fbbe08e8bc84e |
completed | May 9, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69ff2db5dd608190b7b7ba95f19c276c |
completed | May 9, 2026, 12:51 p.m. |
Created at: May 1, 2026, 1:56 a.m.