Triple
T12595929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bochica |
E300729
|
entity |
| Predicate | comparativeMythology |
P93051
|
FINISHED |
| Object | often compared to Viracocha |
—
|
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: often compared to Viracocha | Statement: [Bochica, comparativeMythology, often compared to Viracocha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comparativeMythology Context triple: [Bochica, comparativeMythology, often compared to Viracocha]
-
A.
hasComparativeMyth
chosen
Indicates that one myth is related to another through comparison, analogy, or shared thematic or structural features.
-
B.
subsequentMythology
Indicates that one mythology develops later than, or is derived from, another mythology in time or tradition.
-
C.
mythologicalCategory
Indicates that one entity is classified as belonging to the mythological type, group, or category represented by the other entity.
-
D.
languageOfMyths
Indicates that the subject is the language in which the myths associated with the object are told or recorded.
-
E.
linkedToMythology
Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
- 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954e6e20481908bca684c4b497c48 |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95416cbd88190b2c65196162349bc |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5:08 p.m.