Triple
T35177390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kimmerioi |
E1015745
|
entity |
| Predicate | associatedWithMythicLocation |
P83718
|
FINISHED |
| Object | edge of the world |
—
|
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: edge of the world | Statement: [Kimmerioi, associatedWithMythicLocation, edge of the world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithMythicLocation Context triple: [Kimmerioi, associatedWithMythicLocation, edge of the world]
-
A.
relatedMythicalPlace
chosen
Indicates that one entity has an association or connection with a mythical or legendary place in relation to the other entity.
-
B.
hasMythicSetting
Indicates that something is set within a mythic, legendary, or folklore-based world or context.
-
C.
associatedTribeLocation
Indicates a relationship where a tribe is linked or connected to a specific geographic location.
-
D.
associatedMystic
Indicates a relationship where one entity is linked or connected to another through a mystical, spiritual, or esoteric association.
-
E.
mythologicalLocation
Indicates that the subject is a place or setting that exists within mythology, legends, or folklore rather than in historical or physical reality.
- 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_69f76ddcc108819097f96853b7ed9ef4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.