Triple
T26483783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Mixed-Up Chameleon |
E664762
|
entity |
| Predicate | similarWorkByAuthor |
P98868
|
FINISHED |
| Object | The Very Hungry Caterpillar |
—
|
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: The Very Hungry Caterpillar | Statement: [The Mixed-Up Chameleon, similarWorkByAuthor, The Very Hungry Caterpillar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: similarWorkByAuthor Context triple: [The Mixed-Up Chameleon, similarWorkByAuthor, The Very Hungry Caterpillar]
-
A.
relatedWorkOfCoAuthor
Indicates that one work is related to another through a shared co-author relationship between their creators.
-
B.
followsWorkBySameAuthors
Indicates that one work comes after and is related to another work created by the same authors.
-
C.
relatedWorkSeriesAuthor
Indicates that an author is associated with a work that is part of the same series or a related series as another work.
-
D.
workBySameAuthorAs
chosen
Indicates that two works share the same author, i.e., they were created by the same person or entity.
-
E.
relatedWorkOfPerson
Indicates that a work (such as a publication, project, or creation) is associated with or produced by a particular person.
- 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_69ee883bc85481909885f92415cbce33 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f612fd2bdc8190b5f8bcd31b57186f |
completed | May 2, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 12:29 a.m.