Triple
T27961413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | myth of Cupid and Psyche |
E704584
|
entity |
| Predicate | relatedToFolktaleType |
P116843
|
FINISHED |
| Object | Aarne–Thompson–Uther type ATU 425A |
—
|
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: Aarne–Thompson–Uther type ATU 425A | Statement: [myth of Cupid and Psyche, relatedToFolktaleType, Aarne–Thompson–Uther type ATU 425A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToFolktaleType Context triple: [myth of Cupid and Psyche, relatedToFolktaleType, Aarne–Thompson–Uther type ATU 425A]
-
A.
hasFolkTaleType
chosen
Indicates that an entity (such as a story) is classified as belonging to a particular folk tale type or category.
-
B.
associatedTale
Indicates that one entity is linked or connected to a particular tale, story, or narrative.
-
C.
hasFolkloreType
Indicates that something is associated with, categorized under, or characterized by a particular type of folklore.
-
D.
countryOfFolklore
Indicates the country with which a particular piece or tradition of folklore is associated or from which it originates.
-
E.
includesFolklore
Indicates that one entity contains, incorporates, or features folklore as part of its content or composition.
- 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_69ef841061e48190b5570f9562f7434d |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69ffacdf9f5c8190baef0245edfe87fc |
completed | May 9, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69ffac5e86e08190a1e6da0840a237ad |
completed | May 9, 2026, 9:51 p.m. |
Created at: April 27, 2026, 7:32 p.m.