Triple
T23217816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahadeva |
E580797
|
entity |
| Predicate | associatedRiver |
P165
|
FINISHED |
| Object | Ganga |
—
|
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: Ganga | Statement: [Mahadeva, associatedRiver, Ganga]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ganga Context triple: [Mahadeva, associatedRiver, Ganga]
-
A.
Ganga
Ganga is a queen associated with the ancient Kuru dynasty in Indian epic tradition, often linked to the river goddess personified in the Mahabharata.
-
B.
Ganges
Ganges is a small commune in southern France, located in the Hérault department at the foothills of the Cévennes mountains.
-
C.
Ganges
chosen
The Ganges is a major river in northern India that is considered sacred in Hinduism and supports hundreds of millions of people along its basin.
-
D.
Mata Ganga
Mata Ganga was the wife of the fifth Sikh Guru, Guru Arjan Dev, and the mother of Guru Hargobind, playing a respected role in early Sikh history.
-
E.
Adi Ganga
Adi Ganga is an old, silted distributary of the Hooghly River in Kolkata, historically significant as a sacred waterway and former main channel of the Ganges.
- 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_69e2460389408190be74f41d217799a9 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1916653f08190a7dcbc659c6b6a25 |
completed | April 29, 2026, 5:04 a.m. |
Created at: April 17, 2026, 4:08 p.m.