Triple
T15674858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donald Wilder |
E377413
|
entity |
| Predicate | roleInMeatballs |
P42172
|
FINISHED |
| Object | director of photography |
—
|
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: director of photography | Statement: [Donald Wilder, roleInMeatballs, director of photography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInMeatballs Context triple: [Donald Wilder, roleInMeatballs, director of photography]
-
A.
roleInCoco
Indicates that an entity serves a specific role or function within the context of the COCO dataset or framework.
-
B.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
C.
roleOfPeopleOnIt
Indicates the specific roles or functions that people have in relation to a particular object, event, or context.
-
D.
roleInBun
Indicates that an entity has a specific functional or contextual role within a particular bundle, grouping, or composite structure.
-
E.
playsInRole
chosen
Indicates that an entity performs or appears in a specific role within a production, event, or context.
- 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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f2c996c8190a9ebe0e92608feaa |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8b36a4819081cb5708fe77ef51 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:16 a.m.