Triple
T4962879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Satna |
E111450
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Satna River |
E639596
|
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: Satna River | Statement: [Satna, namedAfter, Satna River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Satna River Context triple: [Satna, namedAfter, Satna River]
-
A.
Satna River
chosen
Satna River is a river in central India that flows through the Satna district of Madhya Pradesh and serves as an important local water source.
-
B.
Shivna River
The Shivna River is a regional river in the Indian state of Madhya Pradesh that flows near the town of Mandsaur and supports its local agriculture and ecology.
-
C.
Shipra River
The Shipra River is a sacred river in central India, especially revered in the city of Ujjain where it is central to major Hindu religious festivals such as the Kumbh Mela.
-
D.
Yantra River
The Yantra River is a significant river in northern Bulgaria that flows through historic towns like Veliko Tarnovo before joining the Danube.
-
E.
Haldi River
The Haldi River is a river in the Indian state of West Bengal that joins the Hooghly River and forms part of the lower Ganges river system.
- 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_69bd4419393c819086319a6fe4bf8542 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd71f3e6148190b99f35734220ffc3 |
completed | March 20, 2026, 4:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7941938a88190be049ad13c45f73f |
completed | March 28, 2026, 8:40 a.m. |
Created at: March 20, 2026, 1:32 p.m.