Triple
T20182197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dharmaputra |
E492755
|
entity |
| Predicate | associatedConcept |
P531
|
FINISHED |
| Object | RajaDharma |
—
|
NE NERFINISHED |
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: RajaDharma | Statement: [Dharmaputra, associatedConcept, RajaDharma]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RajaDharma Context triple: [Dharmaputra, associatedConcept, RajaDharma]
-
A.
Raja
Raja is a traditional Indian royal title historically used by Hindu monarchs and regional rulers.
-
B.
Rajarshi
Rajarshi is an honorific title in ancient Indian tradition denoting a king who has attained the spiritual wisdom and detachment of a sage.
-
C.
Caturmahārāja
Caturmahārāja is the Sanskrit term for the Four Heavenly Kings, powerful guardian deities who protect the four cardinal directions in Buddhist cosmology.
-
D.
Dhanadhipati
Dhanadhipati is an epithet of Kubera, the Hindu god associated with wealth, treasures, and the guardianship of the north.
-
E.
Dharma-raja
chosen
Dharma-raja is a title of the Hindu god Yama in his role as the divine judge who upholds cosmic law and moral order.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e668ef9370819091a8479f811002a9 |
completed | April 20, 2026, 5:57 p.m. |
Created at: April 11, 2026, 11:36 p.m.