Triple
T6708376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viadrus |
E153065
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical river name |
C4613
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: historical river name Context triple: [Viadrus, instanceOf, historical river name]
-
A.
river nickname
A river nickname is an informal, often descriptive or affectionate name given to a river that reflects its characteristics, history, or cultural significance.
-
B.
river designation
A river designation is a classification or label assigned to a river or river segment that defines its legal status, management category, or special protections based on ecological, cultural, navigational, or recreational significance.
-
C.
historical place name
chosen
A historical place name is a designation for a geographic location that reflects its identity, usage, or significance during a specific past period, which may differ from its modern name or boundaries.
-
D.
Vedic hydronym
A Vedic hydronym is a proper name of a river, stream, or other water body attested in the Vedic texts of ancient India, often carrying religious, mythological, or geographical significance.
-
E.
river
A river is a natural flowing body of water, usually freshwater, that moves continuously along a defined channel from higher elevations toward lower ones, often emptying into a sea, lake, or another river.
- F. None of above.
Provenance (1 batch)
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_69c68808d8d8819087369015270788fe |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:06 p.m.