Triple
T37421233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunza River basin |
E929857
|
entity |
| Predicate | flowsIntoViaHunzaRiver |
P91112
|
FINISHED |
| Object | Gilgit River |
—
|
NE NERFINISHED |
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: Gilgit River | Statement: [Hunza River basin, flowsIntoViaHunzaRiver, Gilgit River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowsIntoViaHunzaRiver Context triple: [Hunza River basin, flowsIntoViaHunzaRiver, Gilgit River]
-
A.
flowsIntoViaMainRiver
chosen
Indicates that one water body ultimately flows into another through the course of a primary or main river channel.
-
B.
linkedToRiver
Indicates a relationship where something is physically or functionally connected to, associated with, or dependent on a river.
-
C.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
D.
hasHeadwatersOf
Indicates that a specified location or feature is the source or origin point of a particular river or watercourse.
-
E.
hasHeadwatersIn
Indicates that the source or origin of a river, stream, or similar watercourse is located within a specified geographic 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_69f76ebf0f288190ba198a78341613b8 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.