Triple
T3182400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhavani River |
E66619
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | Bhavani |
E66619
|
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: Bhavani | Statement: [Bhavani River, alsoKnownAs, Bhavani]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bhavani Context triple: [Bhavani River, alsoKnownAs, Bhavani]
-
A.
Bhavani
chosen
Bhavani is a significant river in southern India, known for flowing through Tamil Nadu and contributing majorly to the Kaveri river system.
-
B.
Bhavani
Bhavani is a fierce and protective form of the Hindu goddess Devi, often associated with power, motherhood, and the destruction of evil.
-
C.
Ramavati
Ramavati was a principal urban center that served as the capital city of the medieval Pala Empire in the Indian subcontinent.
-
D.
Arkavathi
Arkavathi is a river in the Indian state of Karnataka that flows through the Bangalore region before joining the Kaveri.
-
E.
Iravati
Iravati is the ancient name of the Ravi River, one of the five major rivers of the Punjab region in South Asia.
- 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_69ad8587c1bc8190a2595f2c22ee1001 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada6bd07888190b680eace8290d821 |
completed | March 8, 2026, 4:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b53fccf644819082334b566f23c20a |
completed | March 14, 2026, 11 a.m. |
Created at: March 8, 2026, 3:06 p.m.