Triple
T19594820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angada |
E470323
|
entity |
| Predicate | mythologicalCycle |
P9595
|
FINISHED |
| Object | Rama-Ravana war |
—
|
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: Rama-Ravana war | Statement: [Angada, mythologicalCycle, Rama-Ravana war]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rama-Ravana war Context triple: [Angada, mythologicalCycle, Rama-Ravana war]
-
A.
Rama–Ravana war
chosen
The Rama–Ravana war is the climactic battle in the Hindu epic Ramayana in which Lord Rama confronts and ultimately defeats the demon king Ravana to rescue his wife Sita.
-
B.
Rama with Sita
Rama with Sita refers to the revered divine couple in Hinduism, embodying the ideals of righteousness, devotion, and marital fidelity.
-
C.
Rama
Rama is a river in Bosnia and Herzegovina that flows through mountainous terrain before joining the Neretva River.
-
D.
Rama
Rama is a common Albanian surname notably borne by Edi Rama, the Prime Minister of Albania.
-
E.
Rama
Rama is a small rural community located in the Canadian province of Saskatchewan.
- 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.