Triple
T34981152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Oneders |
E1008816
|
entity |
| Predicate | managerInFilm |
P192007
|
FINISHED |
| Object | Mr. White |
—
|
NE NERFINISHED |
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: Mr. White | Statement: [The Oneders, managerInFilm, Mr. White]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managerInFilm Context triple: [The Oneders, managerInFilm, Mr. White]
-
A.
leaderInFilm
Indicates that an entity serves as a leading actor, actress, or primary performer in a particular film.
-
B.
ownedByInFilm
Indicates that one entity is portrayed as being owned or possessed by another entity within the context of a specific film.
-
C.
directorAssociatedWith
Indicates a relationship where a director is professionally connected to, responsible for, or involved with a particular entity (such as a work, organization, or project).
-
D.
directorOfWorkFeaturingSubject
Indicates that the subject is the director of a creative work in which another specified entity appears or is featured.
-
E.
castingDirectorOf
Indicates that a person serves as the casting director responsible for selecting the cast of a particular production or project.
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
| PDg | Predicate description generation | batch_69fcf1b241888190a243f07051c71383 |
completed | May 7, 2026, 8:10 p.m. |
Created at: May 3, 2026, 4:01 p.m.