Triple
T4783354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gandiva |
E106417
|
entity |
| Predicate | associatedDeity |
P1481
|
FINISHED |
| Object | Brahma |
E18875
|
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: Brahma | Statement: [Gandiva, associatedDeity, Brahma]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Brahma Context triple: [Gandiva, associatedDeity, Brahma]
-
A.
Brahma
Brahma is a large, hardy domestic chicken breed known for its feathered legs, calm temperament, and good meat and egg production.
-
B.
Brahma
chosen
Brahma is the Hindu god of creation, traditionally regarded as part of the Trimurti alongside Vishnu and Shiva.
-
C.
Purusha
Purusha is the cosmic being or universal spirit in Vedic and later Hindu philosophy, often depicted as the primordial person whose sacrifice gives rise to the universe and social order.
-
D.
Vivasvan
Vivasvan is a Vedic epithet of the Hindu sun god, revered as a solar deity and progenitor of humanity in ancient Indian scriptures.
-
E.
Daksha
Daksha was a ruler who succeeded King Balitung in the line of Mataram (Medang) monarchs in early medieval Java.
- 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_69bd43f4a9588190bf73e20bc27c03cc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd65ad3a188190872e47e3a3bf504b |
completed | March 20, 2026, 3:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69beba49cac08190aa083ebeb52004eb |
completed | March 21, 2026, 3:33 p.m. |
Created at: March 20, 2026, 1:22 p.m.