Triple
T31937193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argonaut Jason |
E815422
|
entity |
| Predicate | assistedByMagic |
P54722
|
FINISHED |
| Object | Medea's spells and potions |
—
|
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: Medea's spells and potions | Statement: [Argonaut Jason, assistedByMagic, Medea's spells and potions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assistedByMagic Context triple: [Argonaut Jason, assistedByMagic, Medea's spells and potions]
-
A.
usesMagic
Indicates that an entity performs actions or achieves effects by employing magical powers or supernatural abilities.
-
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.
enchantedBy
Indicates that one entity has cast or holds a magical enchantment over another entity.
-
D.
wasAssistedBy
Indicates that an entity carried out an action or achieved a result with the help or support of another entity.
-
E.
involvesMagic
chosen
Indicates that the related action, event, or relationship includes the use or presence of magical powers, forces, or phenomena.
- 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_69f348f3035c81908558e2339955abb3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b26d4b5c8190bde4c96bf1860698 |
completed | May 3, 2026, 2:26 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:05 a.m.