Triple
T5647114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kishkindha |
E124411
|
entity |
| Predicate | religionInMyth |
P9595
|
FINISHED |
| Object | Hinduism |
—
|
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: Hinduism | Statement: [Kishkindha, religionInMyth, Hinduism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religionInMyth Context triple: [Kishkindha, religionInMyth, Hinduism]
-
A.
mythologicalCategory
Indicates that one entity is classified as belonging to the mythological type, group, or category represented by the other entity.
-
B.
linkedToMythology
chosen
Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
-
C.
discussesDeity
Indicates that one entity talks or writes about, analyzes, or otherwise engages in discourse concerning a deity or divine being.
-
D.
expandsMythologyOf
Indicates that one entity broadens, enriches, or adds new elements to the mythological background or lore associated with another entity.
-
E.
otherDeity
Indicates that one deity is distinct from and not identical to another deity within a given context or system.
- 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_69c00825df388190a58742fa9b1aa33d |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022abf0108190b10b3a9fe1688bf9 |
completed | March 22, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69c01b2168508190b64b355cf50034ad |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:41 p.m.