Triple
T5876492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raman |
E130637
|
entity |
| Predicate | isRomanizationOf |
P2508
|
FINISHED |
| Object | Rāman |
E130637
|
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: Rāman | Statement: [Raman, isRomanizationOf, Rāman]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rāman Context triple: [Raman, isRomanizationOf, Rāman]
-
A.
Rama
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.
Raman
chosen
Raman is a common Indian surname most famously associated with physicist C. V. Raman, a Nobel laureate known for discovering the Raman effect in light scattering.
-
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_69c0085523688190bfd487479ce819e6 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0362fb6948190bdbb3f1d446d070c |
completed | March 22, 2026, 6:34 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c107fd138c819092096f473be3e4cf |
completed | March 23, 2026, 9:29 a.m. |
Created at: March 22, 2026, 3:57 p.m.