Triple
T15694710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahemdavad |
E380428
|
entity |
| Predicate | locatedOnRiver |
P165
|
FINISHED |
| Object | Vatrak River |
E224270
|
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: Vatrak River | Statement: [Mahemdavad, locatedOnRiver, Vatrak River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vatrak River Context triple: [Mahemdavad, locatedOnRiver, Vatrak River]
-
A.
Vatrak River
chosen
The Vatrak River is a tributary river in western India that flows through the state of Gujarat before joining the Sabarmati River.
-
B.
Strumitsa River
The Strumitsa River is a river in North Macedonia and Bulgaria that flows through the town of Strumica before joining the Struma River.
-
C.
Vishera River
The Vishera River is a significant waterway in Russia’s Perm Krai, known for its scenic, largely untouched natural landscapes and role in the regional river system.
-
D.
Rositsa River
Rositsa River is a river in central northern Bulgaria that flows through the Balkan foothills before joining the Yantra River.
-
E.
Kovzha River
The Kovzha River is a waterway in northwestern Russia that forms part of the navigable route linking the Volga River basin with the Baltic Sea.
- 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04f50ce848190a839c4fb7306d793 |
completed | April 16, 2026, 2:54 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a01c9260c508190aa83d6bed8b598a6 |
completed | May 11, 2026, 12:18 p.m. |
Created at: April 10, 2026, 4:44 a.m.