Triple
T19595178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hindu mythology |
E470331
|
entity |
| Predicate | featuresDeity |
P20396
|
FINISHED |
| Object | Vamana |
—
|
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: Vamana | Statement: [Hindu mythology, featuresDeity, Vamana]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vamana Context triple: [Hindu mythology, featuresDeity, Vamana]
-
A.
Vamana
chosen
Vamana is the dwarf Brahmin incarnation of the Hindu god Vishnu, known for subduing the demon king Bali through a request for three strides of land that he then expansively claimed.
-
B.
Andhaka
Andhaka is a prominent clan within the ancient Yadava lineage of Hindu tradition, often associated with the family and kingdom of Krishna.
-
C.
Anjaneya
Anjaneya is another name for the Hindu deity Hanuman, revered as a symbol of strength, devotion, and selfless service.
-
D.
Surapadman
Surapadman is a powerful demon king in Hindu mythology, best known as the primary adversary defeated by the god Murugan (Skanda) during the events commemorated in the Skanda Sashti festival.
-
E.
Gopala
Gopala is a pastoral form of the Hindu god Krishna, revered especially as a divine cowherd and protector of cows.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640793cd88190b9b84491bfb2493f |
completed | April 20, 2026, 3:04 p.m. |
Created at: April 10, 2026, 1:43 p.m.