Triple
T2188902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E. L. James |
E49814
|
entity |
| Predicate | roleInFilm |
P21967
|
FINISHED |
| Object | producer of Fifty Shades of Grey (film) |
—
|
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: producer of Fifty Shades of Grey (film) | Statement: [E. L. James, roleInFilm, producer of Fifty Shades of Grey (film)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInFilm Context triple: [E. L. James, roleInFilm, producer of Fifty Shades of Grey (film)]
-
A.
playedRoleIn
Indicates that an entity performed or assumed a specific role or character within a particular event, production, or context.
-
B.
partOfFilmographyOf
Indicates that a work (such as a film, show, or role) is included in the body of screen-related works credited to a particular person.
-
C.
hasFictionalRole
Indicates that an entity plays or is assigned a specific role within a fictional work or narrative.
-
D.
hasCrewRole
chosen
Indicates that an entity serves in a specific role or position within a crew associated with another entity.
-
E.
playedKeyRoleIn
Indicates that an entity had a major, influential, or decisive impact on the occurrence, outcome, or success of another entity or event.
- 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_69a88aaba3c48190b351cab9b26989ff |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf9e99f08190892d34485c8f2f25 |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda32d1881909d1fd83a751fb21c |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.