Triple
T5075834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panna |
E114392
|
entity |
| Predicate | river |
P165
|
FINISHED |
| Object | Ken River |
E108472
|
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: Ken River | Statement: [Panna, river, Ken River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ken River Context triple: [Panna, river, Ken River]
-
A.
Ken River
chosen
The Ken River is a significant river in central India that flows through the states of Madhya Pradesh and Uttar Pradesh before joining the Yamuna.
-
B.
Jonk River
The Jonk River is a tributary watercourse in central India that flows through parts of Chhattisgarh and Odisha before joining the larger Mahanadi River system.
-
C.
Tüp River
The Tüp River is a mountain river in northeastern Kyrgyzstan that flows into Lake Issyk-Kul, contributing to the lake’s freshwater inflow.
-
D.
Vuoksi River
The Vuoksi River is a major waterway in northwestern Russia and southeastern Finland, known for connecting Lake Saimaa to Lake Ladoga and playing a key historical and economic role in the region.
-
E.
Clinton River
The Clinton River is a waterway in southeastern Michigan that flows through several communities before emptying into Lake St. Clair.
- 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_69bd443dbf908190a9401e9c2dc7bd7d |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74d2243481908c1ae62f7123c4e9 |
completed | March 20, 2026, 4:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce019fb0cc81908a24b0e39110325d |
completed | April 2, 2026, 5:41 a.m. |
Created at: March 20, 2026, 1:39 p.m.