Triple
T15182155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hydaspes River |
E362771
|
entity |
| Predicate | SanskritName |
P744
|
FINISHED |
| Object | Vitasta |
E145706
|
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: Vitasta | Statement: [Hydaspes River, SanskritName, Vitasta]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vitasta Context triple: [Hydaspes River, SanskritName, Vitasta]
-
A.
Vitasta
chosen
Vitasta is the ancient Sanskrit name for the Jhelum River, a historically significant river of the Kashmir region frequently mentioned in Vedic and classical Indian texts.
-
B.
Vatutine
Vatutine is a small industrial city in central Ukraine, located within Cherkasy Oblast.
-
C.
Vahka
Vahka was a medieval town that served as an early capital of the Armenian Kingdom of Cilicia.
-
D.
Vahalis
Vahalis is an ancient or historical name for the River Waal, a major distributary branch of the Rhine in the Netherlands.
-
E.
Vauhallan
Vauhallan is a small commune in the southern suburbs of Paris, located in the Essonne department in the Île-de-France region of northern France.
- 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_69d85a09a39c81908759f23268e2d408 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e006663ad48190986b680001be0e9b |
completed | April 15, 2026, 9:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fed32a1e3c81909ca2bd431a01e9cf |
completed | May 9, 2026, 6:24 a.m. |
Created at: April 10, 2026, 3:09 a.m.