Triple
T37129011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puppy Co. |
E919466
|
entity |
| Predicate | createdForWorkByStudio |
P65723
|
FINISHED |
| Object | DreamWorks Animation |
—
|
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: DreamWorks Animation | Statement: [Puppy Co., createdForWorkByStudio, DreamWorks Animation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdForWorkByStudio Context triple: [Puppy Co., createdForWorkByStudio, DreamWorks Animation]
-
A.
createdForWorkBy
chosen
Indicates that something was created specifically for use in work or professional activities by a particular agent or person.
-
B.
createdForWorkDirector
Indicates that something was created specifically for use by, or under the direction of, a particular work director.
-
C.
createdByStudioFounder
Indicates that something (such as a work, project, or company) was created by the person who founded the studio.
-
D.
createdByWorkCreator
Indicates that something (such as a work, artifact, or result) was brought into existence by a specific creator or originator.
-
E.
createdWork
Indicates that an agent is responsible for bringing a work (such as a creative, intellectual, or produced artifact) into existence.
- 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_69f76e9d13e48190a108f7fbf80ff375 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffcf46fd688190907fd1ceb499a8d1 |
completed | May 10, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69ffccde2a8c81908e055e74077dbd19 |
completed | May 10, 2026, 12:10 a.m. |
Created at: May 3, 2026, 4:15 p.m.