Triple
T2643747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fairy Godmother |
E62936
|
entity |
| Predicate | transforms |
P26626
|
FINISHED |
| Object | pumpkin into carriage |
—
|
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: pumpkin into carriage | Statement: [Fairy Godmother, transforms, pumpkin into carriage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transforms Context triple: [Fairy Godmother, transforms, pumpkin into carriage]
-
A.
transformsUnder
Indicates a relationship where one entity changes form, state, or structure when subjected to the influence, conditions, or operation specified by another entity.
-
B.
movementTransformed
Indicates that an entity’s movement has been altered or converted from one form, state, or pattern into another.
-
C.
regionTransformed
Indicates that one region has been changed or converted into another region through some transformation process.
-
D.
transition
chosen
Indicates a change of state or condition from one form, phase, or situation to another.
-
E.
coordinateTransformation
Indicates a relationship where one coordinate system is mathematically converted or mapped into another, preserving the correspondence of points between them.
- 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.