Triple
T8559680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamuna |
E202658
|
entity |
| Predicate | epithet |
P743
|
FINISHED |
| Object | Yami |
E218803
|
NE 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: Yami | Statement: [Yamuna, epithet, Yami]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yami Context triple: [Yamuna, epithet, Yami]
-
A.
Yami
chosen
Yami is a figure in Hindu mythology known as the sister of the death god Yama and often associated with early Vedic narratives about sibling relationships and morality.
-
B.
Yami (Tao)
Yami (Tao) is an Austronesian language spoken by the Tao people of Orchid Island, Taiwan, known for its distinct phonology and close relation to the Batanic languages of the Philippines.
-
C.
Miya
Miya is a Japanese honorific suffix historically used in imperial and aristocratic titles, particularly within branches of the Japanese Imperial Family such as the Higashikuni-no-miya.
-
D.
Miya
Miya is a Chadic language spoken in parts of northern Nigeria, known for its complex tonal system and Afroasiatic linguistic roots.
-
E.
Marichi
Marichi is a revered Vedic sage (one of the Saptarishi) regarded as a mind-born son of Brahma and an important progenitor in Hindu cosmology.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca8326e6c881908ff720d6abaebdc5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe949974c8190a75d9c767ca5fa5a |
completed | March 31, 2026, 3:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce894d82588190b558d5b2dc65eafe |
completed | April 2, 2026, 3:20 p.m. |
Created at: March 30, 2026, 6:20 p.m.