Triple
T27000220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eman Esfandi |
E680081
|
entity |
| Predicate | castingAnnouncementForRole |
P161760
|
FINISHED |
| Object | Ezra Bridger in Ahsoka |
—
|
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: Ezra Bridger in Ahsoka | Statement: [Eman Esfandi, castingAnnouncementForRole, Ezra Bridger in Ahsoka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: castingAnnouncementForRole Context triple: [Eman Esfandi, castingAnnouncementForRole, Ezra Bridger in Ahsoka]
-
A.
castingDiscovery
Indicates the process or event in which a casting (e.g., of a role, part, or object) is identified, selected, or revealed.
-
B.
castingNote
Indicates that there is an explanatory note or comment about how a role was cast or performed in a production.
-
C.
castBy
Indicates that one entity (typically a role or character) is portrayed or performed by another entity (typically an actor or performer).
-
D.
cast
Indicates that an agent selects and assigns a person or thing to play a specific role or function in a production or context.
-
E.
castIn
Indicates that an actor or performer appears in a particular film, show, or production.
- 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_69eeeb52908c8190bd246244686aa455 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f621cbc48881908d104c648c91c715 |
completed | May 2, 2026, 4:09 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61f109ef48190873bfe18638d2046 |
completed | May 2, 2026, 3:58 p.m. |
Created at: April 27, 2026, 6:57 a.m.