Triple
T30275625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack Sadelstein |
E769932
|
entity |
| Predicate | playedByAlsoPlays |
P37305
|
FINISHED |
| Object | Jill Sadelstein |
—
|
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: Jill Sadelstein | Statement: [Jack Sadelstein, playedByAlsoPlays, Jill Sadelstein]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedByAlsoPlays Context triple: [Jack Sadelstein, playedByAlsoPlays, Jill Sadelstein]
-
A.
portrayedByAlsoPlays
chosen
Indicates that the actor who portrays a given character also plays another specified role or character.
-
B.
playedBy
Indicates that a role, character, or performance is portrayed or executed by a specific person or agent.
-
C.
arePlayedBy
Indicates that one or more performers (such as actors or musicians) carry out, interpret, or execute the referenced roles, characters, or pieces.
-
D.
oftenPlayedBy
Indicates that one entity frequently performs, portrays, or executes another entity, such as a role, character, or piece of music.
-
E.
alsoPortrayedBy
Indicates that the same role or character is portrayed by an additional, different performer or actor.
- 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_69f224868fa8819099127eaf8855a28f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 29, 2026, 7:44 p.m.