Triple
T20491218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baralacha La |
E502748
|
entity |
| Predicate | nearbyRiverSource |
P8567
|
FINISHED |
| Object | Bhaga River |
E117793
|
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: Bhaga River | Statement: [Baralacha La, nearbyRiverSource, Bhaga River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyRiverSource Context triple: [Baralacha La, nearbyRiverSource, Bhaga River]
-
A.
nearbyRiverProject
Indicates that there is a project located close to or associated with a nearby river.
-
B.
nearbyWatercourse
chosen
Indicates that one entity is located close to or alongside a natural or artificial watercourse, such as a river, stream, or canal.
-
C.
riverLocation
Indicates that a river is located in, passes through, or is geographically associated with a specified place or region.
-
D.
nearbyWaterfall
Indicates that the entity is located close to or within a short distance of a waterfall.
-
E.
hasNearbyRiverStructure
Indicates that a river-related structure (such as a dam, bridge, or levee) is located close to the referenced entity.
- F. None of above.
Provenance (4 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_69e0b4b0373881909dd3e9387f82eab4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69cb8e7848190a1dc497a10ae798c |
completed | April 20, 2026, 9:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0fc98202248190a2e3ee03c4e7078a |
completed | May 22, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69e59fcdf6e08190a604204615dc56e6 |
completed | April 20, 2026, 3:38 a.m. |
Created at: April 16, 2026, 11:35 a.m.