Triple
T2643890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bibbidi-Bobbidi-Boo |
E62939
|
entity |
| Predicate | fictiveFunction |
P33843
|
FINISHED |
| Object | incantation |
—
|
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: incantation | Statement: [Bibbidi-Bobbidi-Boo, fictiveFunction, incantation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictiveFunction Context triple: [Bibbidi-Bobbidi-Boo, fictiveFunction, incantation]
-
A.
fictionalizationOf
Indicates that one entity is a fictional or dramatized representation, adaptation, or reimagining of another (typically real or earlier) entity or event.
-
B.
hasFictionalForm
chosen
Indicates that an entity has a counterpart or representation that exists within a fictional or imaginary context.
-
C.
dramaticFunction
Indicates the role or purpose that something serves within the structure or progression of a dramatic work or narrative.
-
D.
notFunction
Indicates that the specified entity does not serve as a function or is not used in a functional role within the given context.
-
E.
formerFunction
Indicates that an entity previously held a specific role, position, or function but no longer does so.
- 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_69ab4c3f2dcc819082df80f5e032f690 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abd90046dc81908bab3440733f1e98 |
completed | March 7, 2026, 7:51 a.m. |
| PD | Predicate disambiguation | batch_69abd814298c8190952f05aed43f6bb8 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.