Triple
T14536165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pinocchio (Shrek) |
E341047
|
entity |
| Predicate | roleInShrek2 |
P114823
|
FINISHED |
| Object | helps rescue Shrek from Fairy Godmother and Prince Charming |
—
|
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: helps rescue Shrek from Fairy Godmother and Prince Charming | Statement: [Pinocchio (Shrek), roleInShrek2, helps rescue Shrek from Fairy Godmother and Prince Charming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInShrek2 Context triple: [Pinocchio (Shrek), roleInShrek2, helps rescue Shrek from Fairy Godmother and Prince Charming]
-
A.
roleInMulan
Indicates that one entity has a specific role or part in the context of "Mulan" (such as the film, story, or production).
-
B.
roleInJaws2
Indicates that an entity had a role or participation in the movie *Jaws 2*.
-
C.
roleInBladeII
Indicates that an entity has a specific role or participation in the movie "Blade II."
-
D.
roleInZootopia
Indicates that an entity has a specific role, function, or position within the context of Zootopia.
-
E.
roleInMonsterVerse
Indicates that an entity has a specific role or function within the MonsterVerse franchise or universe.
- F. None of above. chosen
Provenance (4 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb1b9d39881908c7a3a5b17d432af |
completed | April 14, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69de5c546c7081909e27d504ec360c5c |
completed | April 14, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69de610330a48190b558235a14c0dc9f |
completed | April 14, 2026, 3:45 p.m. |
Created at: April 10, 2026, 1:22 a.m.