Triple
T33465640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michigan J. Frog |
E857033
|
entity |
| Predicate | animationDirectorOfDebut |
P53227
|
FINISHED |
| Object | Chuck Jones |
—
|
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: Chuck Jones | Statement: [Michigan J. Frog, animationDirectorOfDebut, Chuck Jones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: animationDirectorOfDebut Context triple: [Michigan J. Frog, animationDirectorOfDebut, Chuck Jones]
-
A.
firstProductionDirector
Indicates that the object is the person who first served as production director for the subject.
-
B.
featureDirectorialDebutOf
Indicates that a work (typically a film) serves as the first directorial effort of a particular director.
-
C.
directorOfFirstAppearance
chosen
Indicates that a person is the director responsible for an entity’s first appearance (e.g., first episode, film, or installment) in a series or franchise.
-
D.
animeDirector
Indicates that one entity is the director of an anime work associated with the other entity.
-
E.
workedAsDirectorFor
Indicates that one entity held the role of director in relation to another entity, such as an organization, project, or production.
- 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_69f34973461481909c701c98ebd75623 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e4f996948190a20e96059d5188cc |
completed | May 3, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:37 a.m.