Triple
T10223207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trimbak |
E242633
|
entity |
| Predicate | riverOriginType |
P25636
|
FINISHED |
| Object | sacred river source |
—
|
LITERAL 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: sacred river source | Statement: [Trimbak, riverOriginType, sacred river source]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverOriginType Context triple: [Trimbak, riverOriginType, sacred river source]
-
A.
majorRiverSource
Indicates that one entity is the primary originating source or headwaters location of a major river.
-
B.
hasHydronymOrigin
Indicates that something derives its name from a body of water or hydrological feature.
-
C.
sourceOfWatercourse
chosen
Indicates that one entity is the origin or starting point from which a watercourse (such as a river or stream) begins or flows.
-
D.
riverSystem
Indicates that one entity is a river system to which the other entity belongs or is a component (such as a tributary or segment).
-
E.
isWatercourseOf
Indicates that a watercourse (such as a river or stream) flows through, belongs to, or is geographically associated with a particular area or feature.
- F. None of above.
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_69d381ae26c48190985abd0e25ee5d04 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d3aa8305e481908ee1fc1d9eda6fa0 |
completed | April 6, 2026, 12:43 p.m. |
| PD | Predicate disambiguation | batch_69d3955f61f88190b8d37ff645cd44d3 |
completed | April 6, 2026, 11:13 a.m. |
Created at: April 6, 2026, 11:10 a.m.