Triple
T33422517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Outstanding Supporting Actor in a Drama Series |
E855881
|
entity |
| Predicate | isSeparatedByRoleSize |
P177023
|
FINISHED |
| Object | supporting |
—
|
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 | Statement: [Outstanding Supporting Actor in a Drama Series, isSeparatedByRoleSize, supporting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSeparatedByRoleSize Context triple: [Outstanding Supporting Actor in a Drama Series, isSeparatedByRoleSize, supporting]
-
A.
hasRoleDistribution
Indicates how roles, responsibilities, or functions are allocated or distributed among entities within a given context.
-
B.
includesRoles
Indicates that one entity contains or encompasses one or more specified roles within its scope or structure.
-
C.
providesSeparationFor
Indicates that one entity serves to divide, isolate, or keep another entity apart from something else.
-
D.
separatedIn
Indicates that two or more entities, once together or associated, have been divided, split, or otherwise placed into distinct parts, groups, or locations.
-
E.
hasRelativeRole
Indicates that one entity holds a familial or kinship-based role in relation to another entity.
- 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_69f3496fdf0081908c1aa30870ce518b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f85bfba48190aba95b40642a8ca7 |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f814fcf48190ae4504154d1b2c05 |
completed | May 3, 2026, 7:24 a.m. |
Created at: May 1, 2026, 1:36 a.m.