Triple
T31520480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhinemaidens |
E804192
|
entity |
| Predicate | mythologicalAnalog |
P54299
|
FINISHED |
| Object | Rhine maidens (folklore) |
—
|
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: Rhine maidens (folklore) | Statement: [Rhinemaidens, mythologicalAnalog, Rhine maidens (folklore)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mythologicalAnalog Context triple: [Rhinemaidens, mythologicalAnalog, Rhine maidens (folklore)]
-
A.
mythologicalContent
Indicates that the subject contains, references, or is associated with myths, mythological narratives, or myth-based elements.
-
B.
mythologicalCategory
chosen
Indicates that one entity is classified as belonging to the mythological type, group, or category represented by the other entity.
-
C.
mythologized
Indicates that one entity has been turned into or treated as a mythic, legendary, or highly idealized figure or story by another.
-
D.
mythologicalRole
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
-
E.
mythologicalSetting
Indicates that an entity is set within, associated with, or takes place in a mythological or legendary context.
- 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_69f348cf839c81908657048402f7f97b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 9:55 p.m.