Triple
T16751148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bill Truitt |
E407081
|
entity |
| Predicate | featuredInPlotElement |
P114831
|
FINISHED |
| Object | manipulation |
—
|
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: manipulation | Statement: [Bill Truitt, featuredInPlotElement, manipulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredInPlotElement Context triple: [Bill Truitt, featuredInPlotElement, manipulation]
-
A.
featuredElement
Indicates that one element is highlighted or given special prominence relative to others in a given context.
-
B.
featuredIn
Indicates that one entity appears or is prominently included within another entity, such as a person, work, or item being showcased in a larger work, event, or context.
-
C.
introducesPlotElement
Indicates that an entity brings a new story component, twist, or development into the narrative.
-
D.
plotElementInEpisode
chosen
Indicates that a specific plot element appears within or is part of a particular episode.
-
E.
plotElement
Indicates that one entity functions as a narrative component or structural element within the storyline of another entity (such as a work of fiction or media).
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3aa271de48190b4a535408aeef734 |
completed | April 18, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.