Triple
T19463037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles E. Ford |
E486921
|
entity |
| Predicate | roleInFilmProduction |
P136019
|
FINISHED |
| Object | producer |
—
|
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 | Statement: [Charles E. Ford, roleInFilmProduction, producer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInFilmProduction Context triple: [Charles E. Ford, roleInFilmProduction, producer]
-
A.
roleInCinerama
Indicates that an entity has a role or participation in a Cinerama film or production.
-
B.
roleInFilmEcosystem
Indicates the specific function or position an entity holds within the broader network of activities, stakeholders, and processes that make up the film ecosystem.
-
C.
subsidiaryRoleOfGeneralFilmCompany
Indicates that an entity serves as a subsidiary or subordinate unit within the General Film Company.
-
D.
cinematographerOfWork
Indicates that a person served as the cinematographer (director of photography) for a specific creative work.
-
E.
producedRole
Indicates that one entity was responsible for creating, originating, or bringing about a particular role associated with 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633cd6c148190933b4d6bfe84cbe1 |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:38 p.m.