Triple
T2600935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heavenly Kings Hall |
E58340
|
entity |
| Predicate | associatedDeity |
P1481
|
FINISHED |
| Object | Vaiśravaṇa |
E103309
|
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: Vaiśravaṇa | Statement: [Heavenly Kings Hall, associatedDeity, Vaiśravaṇa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vaiśravaṇa Context triple: [Heavenly Kings Hall, associatedDeity, Vaiśravaṇa]
-
A.
Yamaraja
Yamaraja is the Hindu god of death and justice, who judges the souls of the dead and presides over the afterlife.
-
B.
Kubera
chosen
Kubera is the Hindu god of wealth and the treasurer of the gods, revered as the lord of riches and prosperity.
-
C.
Jade Emperor
The Jade Emperor is the supreme ruler of heaven and all realms of existence in Chinese folk religion and Taoist tradition, overseeing gods, spirits, and mortals.
-
D.
Hachiman
Hachiman is a major Shinto deity revered as the god of war and the divine protector of Japan and its people, especially warriors.
-
E.
Indra
Indra is the king of the gods and lord of storms, war, and the heavens in ancient Vedic and Hindu mythology.
- 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_69ab4ac14040819098b13f4a27d5c8ff |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd4587014819089f78e93adf2144c |
completed | March 7, 2026, 7:31 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af83d37de081909467f8caa17ce3a9 |
completed | March 10, 2026, 2:37 a.m. |
Created at: March 6, 2026, 9:49 p.m.