Triple
T28038066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johannes "Jojo" Betzler |
E708465
|
entity |
| Predicate | imaginaryFriend |
P95848
|
FINISHED |
| Object | Adolf Hitler (imaginary) |
—
|
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: Adolf Hitler (imaginary) | Statement: [Johannes "Jojo" Betzler, imaginaryFriend, Adolf Hitler (imaginary)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imaginaryFriend Context triple: [Johannes "Jojo" Betzler, imaginaryFriend, Adolf Hitler (imaginary)]
-
A.
hasImaginaryFriendCharacter
chosen
Indicates that an entity is associated with or has an imaginary friend character.
-
B.
imaginaryEnemy
Indicates that one entity regards another as an enemy that exists only in imagination rather than in reality.
-
C.
imaginaryWorld
Indicates a relationship where an entity exists within, belongs to, or is associated with a fictional or imagined world rather than the real one.
-
D.
fictionalCharacter
Indicates that one entity is a fictional character that appears within the narrative world of another entity (such as a work, series, or franchise).
-
E.
isFriendOfProtagonist
Indicates that one entity is a friend or close ally of the story’s main character.
- 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_69ef9b6cf538819094a633ffa67afec1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f63f2e1a248190a41f02f91e8c1183 |
completed | May 2, 2026, 6:15 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 8:22 p.m.