Triple
T13307378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helikon |
E316969
|
entity |
| Predicate | relatedMythicTheme |
P24831
|
FINISHED |
| Object | inspiration from sacred springs |
—
|
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: inspiration from sacred springs | Statement: [Helikon, relatedMythicTheme, inspiration from sacred springs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedMythicTheme Context triple: [Helikon, relatedMythicTheme, inspiration from sacred springs]
-
A.
hasMythicTheme
chosen
Indicates that something embodies, references, or is characterized by a mythic or mythological theme.
-
B.
linkedToMythology
Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
-
C.
relatedMythicalPlace
Indicates that one entity has an association or connection with a mythical or legendary place in relation to the other entity.
-
D.
relatedMythicalPlace
Indicates that one entity has an association or connection with a mythical or legendary place represented by the other entity.
-
E.
associatedMystic
Indicates a relationship where one entity is linked or connected to another through a mystical, spiritual, or esoteric association.
- 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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6893708190aeebf4c47386cff7 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:29 p.m.