Triple
T8559669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamuna |
E202658
|
entity |
| Predicate | sibling |
P363
|
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: [Yamuna, sibling, Yama]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yama Context triple: [Yamuna, sibling, 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.
Yama
Yama is a Linux Security Module that enhances process and ptrace-related security by restricting how processes can inspect or interfere with each other.
-
C.
Yama
Yama is the historical name of the Russian town now known as Kingisepp, located in Leningrad Oblast near the border with Estonia.
-
D.
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.
-
E.
Sonamura
Sonamura is a town in the Indian state of Tripura, known as an administrative and commercial center near the India–Bangladesh border.
- 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.