Triple
T26301523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Achoron |
E661570
|
entity |
| Predicate | equivalentInMythology |
P141581
|
FINISHED |
| Object | Achamán |
—
|
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: Achamán | Statement: [Achoron, equivalentInMythology, Achamán]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equivalentInMythology Context triple: [Achoron, equivalentInMythology, Achamán]
-
A.
equivalentInRomanMythology
Indicates that one entity corresponds to or is identified as the Roman-mythology counterpart of another entity from a different mythological tradition.
-
B.
equivalentMythologicalName
chosen
Indicates that two entities share the same identity in mythology, representing different names or versions of the same mythological figure.
-
C.
equivalentInGreekReligion
Indicates that two religious figures, concepts, or practices are counterparts or direct analogues of each other within the context of Greek religion.
-
D.
linkedToMythology
Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
-
E.
comparableDeity
Indicates that one deity is considered comparable to another in terms of role, attributes, status, or function.
- 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 26, 2026, 10:16 p.m.