Triple
T26052324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kitty in Cocoon: The Return |
E648013
|
entity |
| Predicate | characterOriginWork |
P34184
|
FINISHED |
| Object | Cocoon |
—
|
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: Cocoon | Statement: [Kitty in Cocoon: The Return, characterOriginWork, Cocoon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterOriginWork Context triple: [Kitty in Cocoon: The Return, characterOriginWork, Cocoon]
-
A.
characterOrigin
chosen
Indicates the source, background, or initial context from which a character originates.
-
B.
basedOnCharacterFromWork
Indicates that one entity is derived from, inspired by, or modeled after a character that appears in another creative work.
-
C.
originatedInWorkBy
Indicates that something was created, derived, or first appeared within a particular work produced by a specific creator.
-
D.
genreOfOriginWork
Indicates that a work is classified under a particular genre based on the genre of its original source work.
-
E.
originalLanguageOfCharacterWork
Indicates that a language is the original language in which a particular character-related work (e.g., story, script, or media) was created or first expressed.
- 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_69e77e8d419481908004e6318d28aaab |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 22, 2026, 9:11 a.m.