Triple
T30003350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Searching for Debra Winger |
E762231
|
entity |
| Predicate | hasCastRoleType |
P69823
|
FINISHED |
| Object | actresses playing themselves |
—
|
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: actresses playing themselves | Statement: [Searching for Debra Winger, hasCastRoleType, actresses playing themselves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCastRoleType Context triple: [Searching for Debra Winger, hasCastRoleType, actresses playing themselves]
-
A.
hasCastCharacter
Indicates that a media work includes a specific character as part of its cast.
-
B.
hasCast
Indicates that a creative work features a particular group of performers or actors.
-
C.
hasPlayingRole
Indicates that an entity participates in an activity, event, or performance in a specific playing role or capacity.
-
D.
hasHumanCharacterRole
Indicates that an entity is assigned a role or function specifically associated with a human character within a context such as a story, performance, or representation.
-
E.
hasCastType
chosen
Indicates that an entity participates in a production with a specified type of casting role (e.g., lead, supporting, cameo).
- 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_69f2246a47ac81909cf5213053687ffc |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
Created at: April 29, 2026, 6:42 p.m.