Triple
T35445346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Return from Cythera |
E1024466
|
entity |
| Predicate | refersToMythologicalPlace |
P83718
|
FINISHED |
| Object | Cythera |
—
|
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: Cythera | Statement: [Return from Cythera, refersToMythologicalPlace, Cythera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToMythologicalPlace Context triple: [Return from Cythera, refersToMythologicalPlace, Cythera]
-
A.
mythologicalLocation
Indicates that the subject is a place or setting that exists within mythology, legends, or folklore rather than in historical or physical reality.
-
B.
relatedMythicalPlace
chosen
Indicates that one entity has an association or connection with a mythical or legendary place in relation to the other entity.
-
C.
mythicalBirthplaceOf
Indicates the legendary or mythological location where an entity is said to have originated or been born.
-
D.
linkedToMythology
Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
-
E.
mythologicalTextMention
Indicates that a mythological text mentions, references, or otherwise explicitly refers to a given entity or concept.
- 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_69f76df8089481909f0018266ee881b7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe6c811bcc81908b1e1b1f8bcb071b |
completed | May 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69fe6c026d5481908b7a814dcf38c183 |
completed | May 8, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:04 p.m.