Triple
T9997805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toff Guy Films |
E197246
|
entity |
| Predicate | workRoleInRocknRolla |
P91497
|
FINISHED |
| Object | production company |
—
|
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: production company | Statement: [Toff Guy Films, workRoleInRocknRolla, production company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workRoleInRocknRolla Context triple: [Toff Guy Films, workRoleInRocknRolla, production company]
-
A.
talentShowRole
Indicates the specific function or position an entity holds within the context of a talent show (e.g., performer, judge, host).
-
B.
musicalRole
Indicates the specific function or part an entity performs within a musical context, such as in a performance, composition, or ensemble.
-
C.
typicalPerformerRoleType
Indicates the usual or characteristic role type that a performer commonly plays or is associated with in their performances.
-
D.
musicIndustryRole
Indicates the professional function or position an entity holds within the music industry ecosystem.
-
E.
playsInRole
Indicates that an entity performs or appears in a specific role within a production, event, or context.
- 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_69ca82f3b61c81908ecc2c1c96dbc2e4 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdcc8aa1a881909879a694496f11a5 |
completed | April 2, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69cd1da07db88190945bcdab3ca82e71 |
completed | April 1, 2026, 1:29 p.m. |
| PDg | Predicate description generation | batch_69cd358386f48190833c862b5b8c04b2 |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:51 p.m.