Triple
T24654433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Δανάη |
E610346
|
entity |
| Predicate | hasMythologicalUsage |
P156920
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Δανάη, hasMythologicalUsage, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMythologicalUsage Context triple: [Δανάη, hasMythologicalUsage, yes]
-
A.
hasMythologicalBasis
Indicates that something is founded on, derived from, or significantly influenced by a mythological story, figure, or tradition.
-
B.
hasMythologicalFeature
Indicates that an entity possesses a characteristic, attribute, or element derived from mythology or mythological beings.
-
C.
hasMythologicalDomain
Indicates that a mythological figure, deity, or entity is associated with or rules over a particular conceptual or physical domain (such as the sea, war, or the underworld).
-
D.
hasMythologicalNamesake
Indicates that one entity is named after, or shares its name with, a figure or element from mythology.
-
E.
isMythical
Indicates that the entity is considered mythical, existing only in legend, folklore, or imagination rather than in reality.
- F. None of above. chosen
Provenance (4 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_69e2c4d453248190a020354e93ef6282 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
| PDg | Predicate description generation | batch_69f41010f06c81908ee7f773220df14f |
completed | May 1, 2026, 2:29 a.m. |
Created at: April 18, 2026, 2:34 a.m.