Triple
T902578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vishnu |
E19477
|
entity |
| Predicate | avatar |
P20182
|
FINISHED |
| Object | Rama |
E103308
|
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: Rama | Statement: [Vishnu, avatar, Rama]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rama Context triple: [Vishnu, avatar, Rama]
-
A.
Rama
chosen
Rama is a major Hindu deity and the virtuous prince-king of Ayodhya, revered as the seventh avatar of Vishnu and hero of the epic Ramayana.
-
B.
Ramachandra
Ramachandra, better known as Tatya Tope, was a prominent Indian general and key leader of the 1857 Indian Rebellion against British rule.
-
C.
Vibhishana
Vibhishana is a virtuous rakshasa prince in the Hindu epic Ramayana, known for abandoning his brother Ravana to ally with Rama and uphold dharma.
-
D.
Hanuman
Hanuman is a revered Hindu deity known for his immense strength, unwavering devotion to Lord Rama, and central role in the epic Ramayana.
-
E.
Krishna
Krishna is a major Hindu deity revered as the eighth avatar of Vishnu and celebrated for his roles as a divine lover, charioteer, and teacher in texts like the Bhagavad Gita and the Mahabharata.
- 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_69a4939e889c8190ac148b3ac1a7f90b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b2b9339081909af5ab231be39bb0 |
completed | March 1, 2026, 9:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac16f9d07c819097b9cf95d2b708f7 |
completed | March 7, 2026, 12:15 p.m. |
Created at: March 1, 2026, 7:39 p.m.