Triple
T26778589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Margolotte |
E670187
|
entity |
| Predicate | usedMagicalRecipeOn |
P164295
|
FINISHED |
| Object | Patchwork Girl |
—
|
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: Patchwork Girl | Statement: [Margolotte, usedMagicalRecipeOn, Patchwork Girl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedMagicalRecipeOn Context triple: [Margolotte, usedMagicalRecipeOn, Patchwork Girl]
-
A.
usedSpell
Indicates that one entity has cast or employed a particular spell on or in relation to another entity or context.
-
B.
usesMagicFor
Indicates that one entity employs or applies magic as a means to achieve, affect, or perform something involving another entity or context.
-
C.
usesMagic
Indicates that an entity performs actions or achieves effects by employing magical powers or supernatural abilities.
-
D.
usedForSpell
Indicates that something serves as a component, tool, or resource employed in performing or casting a spell.
-
E.
usesRecipeOf
Indicates that one entity prepares or creates something by following the recipe or formula originally defined or used by another entity.
- 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_69eeb31c925881909b597f6e40056d28 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f644de4a84819087ddb84757fc4585 |
completed | May 2, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f643e818d481908fc66bc91bd25d77 |
completed | May 2, 2026, 6:35 p.m. |
Created at: April 27, 2026, 4:07 a.m.