Triple
T34792065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diamonds and Toads |
E1002972
|
entity |
| Predicate | hasFairyTaleType |
P116843
|
FINISHED |
| Object | moralizing fairy tale |
—
|
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: moralizing fairy tale | Statement: [Diamonds and Toads, hasFairyTaleType, moralizing fairy tale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFairyTaleType Context triple: [Diamonds and Toads, hasFairyTaleType, moralizing fairy tale]
-
A.
hasFolkTaleType
chosen
Indicates that an entity (such as a story) is classified as belonging to a particular folk tale type or category.
-
B.
hasFictionalType
Indicates that an entity is associated with or classified under a particular type or category that is fictional rather than real.
-
C.
hasFairyCharacters
Indicates that the subject includes or features characters that are fairies.
-
D.
hasFolkloreStatus
Indicates that something is recognized or classified as having a status or role within folklore or traditional cultural narratives.
-
E.
hasMythType
Indicates that an entity is associated with or classified under a particular type or category of myth.
- 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_69f76db47d408190a24fc7164439ea2d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
Created at: May 3, 2026, 3:59 p.m.