Triple
T38465644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electra (stage production) |
E912557
|
entity |
| Predicate | characterInTitleRole |
P144142
|
FINISHED |
| Object | Electra |
—
|
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: Electra | Statement: [Electra (stage production), characterInTitleRole, Electra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterInTitleRole Context triple: [Electra (stage production), characterInTitleRole, Electra]
-
A.
portrayedTitleCharacter
chosen
Indicates that one entity played the main or title role character associated with another entity (such as a work or production).
-
B.
characterTitle
Indicates that a character holds or is associated with a specific title, rank, or formal designation.
-
C.
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.
-
D.
hasPortrayedPersonTitle
Indicates that a work or depiction features a portrayed person who holds or is associated with a specific title.
-
E.
directorCharacterOf
Indicates that a director is responsible for directing a particular character in a work (e.g., film, TV show, or play).
- 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_69f76e861d8c81908559031dc66e3c15 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00233e2170819084bee0c8f74cc1a4 |
completed | May 10, 2026, 6:18 a.m. |
| PD | Predicate disambiguation | batch_6a0022943fd08190b73007f080d5971d |
completed | May 10, 2026, 6:15 a.m. |
Created at: May 3, 2026, 4:31 p.m.