Triple
T31102968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clarence Derwent Award |
E792721
|
entity |
| Predicate | awardedForRoleType |
P103839
|
FINISHED |
| Object | supporting actor |
—
|
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: supporting actor | Statement: [Clarence Derwent Award, awardedForRoleType, supporting actor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awardedForRoleType Context triple: [Clarence Derwent Award, awardedForRoleType, supporting actor]
-
A.
hasAwardedRoleType
chosen
Indicates that an entity has been granted or assigned a role of a specified type as an award or honor.
-
B.
responsibleForAwardType
Indicates that an entity has responsibility for granting, managing, or overseeing a particular type or category of award.
-
C.
awardingOrganizationRole
Indicates that an entity holds a specific role or capacity within the organization that grants or confers an award.
-
D.
appliesToAwardType
Indicates that a rule, condition, or attribute is specifically relevant or applicable to a particular type or category of award.
-
E.
hasAwarderRole
Indicates that an entity serves in the role or capacity of granting or conferring an award to another entity.
- 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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: April 29, 2026, 9:03 p.m.