Triple
T5119128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Podolsk |
E115415
|
entity |
| Predicate | locatedOnRiver |
P165
|
FINISHED |
| Object | Pakhra River |
E154144
|
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: Pakhra River | Statement: [Podolsk, locatedOnRiver, Pakhra River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pakhra River Context triple: [Podolsk, locatedOnRiver, Pakhra River]
-
A.
Pakhra River
chosen
The Pakhra River is a tributary waterway in the Moscow region of Russia that feeds into the larger Moskva River system.
-
B.
Pahuj River
The Pahuj River is a tributary of the Yamuna River flowing through the Bundelkhand region of northern India, including the city of Jhansi.
-
C.
Sukhona River
The Sukhona River is a major waterway in northwestern Russia that flows through Vologda Oblast and forms part of the Northern Dvina river system.
-
D.
Karha River
The Karha River is a river in the Indian state of Maharashtra that flows through the Baramati region and supports its agriculture and local communities.
-
E.
Nazia River
The Nazia River is a smaller watercourse in northwestern Russia that serves as a tributary within the Tosna River basin.
- 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_69bd4442ade0819087b9461f892b206b |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd77cf6590819081488b739efae32c |
completed | March 20, 2026, 4:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7daed5d188190b499151e636d206d |
completed | March 28, 2026, 1:43 p.m. |
Created at: March 20, 2026, 1:42 p.m.