Triple
T37668201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Great Piggy Bank Robbery |
E937877
|
entity |
| Predicate | hasFictionalAliasForProtagonist |
P86336
|
FINISHED |
| Object | Duck Twacy |
—
|
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: Duck Twacy | Statement: [The Great Piggy Bank Robbery, hasFictionalAliasForProtagonist, Duck Twacy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalAliasForProtagonist Context triple: [The Great Piggy Bank Robbery, hasFictionalAliasForProtagonist, Duck Twacy]
-
A.
hasFictionalAlias
Indicates that an entity is known by an alternative name or identity within a fictional context.
-
B.
hasFictionalAlterEgoOf
chosen
Indicates that one entity is the fictional alter ego, persona, or alternate identity of another entity.
-
C.
hasFictionalTitleOfProtagonist
Indicates that an entity holds or is assigned the fictional title or role used to designate the main protagonist in a narrative.
-
D.
namedAfterFictionalCharacter
Indicates that one entity has been given its name in honor of, or derived from, a fictional character.
-
E.
isFictionalPersonFrom
Indicates that a fictional person originates from or is associated with a particular place or source.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a006fe981488190b4287289a3327664 |
completed | May 10, 2026, 11:45 a.m. |
| PD | Predicate disambiguation | batch_6a006f6976ec8190ba2c04fbaa946345 |
completed | May 10, 2026, 11:43 a.m. |
Created at: May 3, 2026, 4:18 p.m.