Triple
T502327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern India |
E10427
|
entity |
| Predicate | hasMajorRiver |
P165
|
FINISHED |
| Object | Ganges |
E4044
|
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: Ganges | Statement: [Northern India, hasMajorRiver, Ganges]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ganges Context triple: [Northern India, hasMajorRiver, Ganges]
-
A.
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.
-
B.
Namami Gange
Namami Gange is an Indian government flagship initiative aimed at cleaning, rejuvenating, and protecting the Ganges River and its ecosystem.
-
C.
Jamuna River
The Jamuna River is the main distributary channel of the Brahmaputra in Bangladesh, forming one of the country’s largest and most dynamic river systems.
-
D.
Jamuna
Jamuna is an alternative name for the Yamuna, one of the major sacred rivers of northern India that flows through cities such as Delhi and Agra.
-
E.
Dakshin Ganga
Dakshin Ganga is an honorific name for the Godavari River, revered as a sacred and major waterway of southern and central India akin to the Ganges in the north.
- 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_69a2e848adf881908e5e04f7af030093 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1339748819089f89691a1698dd9 |
completed | Feb. 28, 2026, 1:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a4854692348190b87efc0d4559f63f |
completed | March 1, 2026, 6:28 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.