Triple
T30890684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Nixie of the Mill-Pond |
E786887
|
entity |
| Predicate | taleTypeClassification |
P116843
|
FINISHED |
| Object | Aarne–Thompson–Uther type 316 |
—
|
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: Aarne–Thompson–Uther type 316 | Statement: [The Nixie of the Mill-Pond, taleTypeClassification, Aarne–Thompson–Uther type 316]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taleTypeClassification Context triple: [The Nixie of the Mill-Pond, taleTypeClassification, Aarne–Thompson–Uther type 316]
-
A.
taleTypeName
Indicates the specific category or classification label assigned to a tale or story type.
-
B.
hasFolkTaleType
chosen
Indicates that an entity (such as a story) is classified as belonging to a particular folk tale type or category.
-
C.
narrativeType
Indicates the specific kind or category of narrative (e.g., genre, structural form, or storytelling mode) associated with an entity.
-
D.
fandomClassification
Indicates how an entity is categorized or grouped within a particular fandom or fan community.
-
E.
fictionalType
Indicates that one entity is a fictional or imaginary type or category of the other entity.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:49 p.m.