Triple
T1803079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yam Dwitiya |
E39761
|
entity |
| Predicate | associatedDeity |
P1481
|
FINISHED |
| Object | Yama |
E42391
|
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: Yama | Statement: [Yam Dwitiya, associatedDeity, Yama]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yama Context triple: [Yam Dwitiya, associatedDeity, Yama]
-
A.
Yama
chosen
Yama is the Hindu god of death and justice, traditionally regarded as the ruler of the afterlife and judge of the souls of the dead.
-
B.
Yamate
Yamate is a historic hillside district in Yokohama known for its Western-style residences, foreign settlers’ heritage, and scenic views over the city and harbor.
-
C.
Moruya
Moruya is a coastal town in New South Wales, Australia, known for its scenic river setting, nearby beaches, and historic granite quarries.
-
D.
Wonokitri
Wonokitri is a village in East Java, Indonesia, known as a gateway settlement for visitors heading to the Mount Bromo area.
-
E.
Oya
Oya is a powerful Yoruba orisha associated with storms, winds, transformation, and the Niger River.
- 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_69a88632aa588190ba3978fde0db5bbd |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69aa659535448190b60cb4b0ad2972b6 |
completed | March 6, 2026, 5:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adc9a799fc81909acb620f3e569265 |
completed | March 8, 2026, 7:10 p.m. |
Created at: March 4, 2026, 7:32 p.m.