Triple
T20054082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mary Poppins Opens the Door |
E499282
|
entity |
| Predicate | hasImaginaryElement |
P138526
|
FINISHED |
| Object | talking animals |
—
|
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: talking animals | Statement: [Mary Poppins Opens the Door, hasImaginaryElement, talking animals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImaginaryElement Context triple: [Mary Poppins Opens the Door, hasImaginaryElement, talking animals]
-
A.
isImaginary
Indicates that something exists only in the mind or imagination and does not have a corresponding real-world or physical existence.
-
B.
isPurelyImaginary
Indicates that the entity exists only in imagination or theory and has no real or physical existence.
-
C.
hasRealComponents
Indicates that an entity possesses components or parts whose values are real (non-complex) numbers.
-
D.
imaginaryPart
Indicates the relationship that maps a complex-valued entity to the value of its imaginary component.
-
E.
hasComplexEmbeddings
Indicates that an entity is associated with or represented by complex-valued vector embeddings in some embedding space.
- 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66331c7488190840d43792ff09977 |
completed | April 20, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc20888819083c9118a09d0d2dc |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 3:38 p.m.