Triple
T7430919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramanandi Sampradaya |
E171485
|
entity |
| Predicate | worships |
P1194
|
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: [Ramanandi Sampradaya, worships, Rama]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rama Context triple: [Ramanandi Sampradaya, worships, 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.
Rama
Rama is a small scenic village in Pakistan’s Gilgit-Baltistan region, known as a gateway to the lush Rama Meadows and views of Nanga Parbat.
-
C.
Rama
Rama is a river in Bosnia and Herzegovina that flows through mountainous terrain before joining the Neretva River.
-
D.
Ramachandra
Ramachandra, better known as Tatya Tope, was a prominent Indian general and key leader of the 1857 Indian Rebellion against British rule.
-
E.
Ramachandra
Ramachandra is a common Indian male given name of Sanskrit origin, often associated with the Hindu deity Lord Rama.
- 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_69c68a63491881909281f73d4d5643bf |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f32324c481908c9ba594e8456728 |
completed | March 27, 2026, 9:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c827829a848190afca7b5f79c51c7c |
completed | March 28, 2026, 7:09 p.m. |
Created at: March 27, 2026, 3:12 p.m.