Triple
T3578450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koshi River |
E75742
|
entity |
| Predicate | floodCharacteristic |
P25274
|
FINISHED |
| Object | frequent course changes |
—
|
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: frequent course changes | Statement: [Koshi River, floodCharacteristic, frequent course changes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floodCharacteristic Context triple: [Koshi River, floodCharacteristic, frequent course changes]
-
A.
hydrologicalCharacteristic
chosen
Indicates a relationship where a hydrological feature or condition (such as water flow, level, or behavior) characterizes or describes another entity.
-
B.
hydrologyFeature
Indicates a relationship where one entity is a hydrological feature (such as a body or flow of water) associated with or characterizing another entity.
-
C.
floodEvent
Indicates an occurrence of a flooding event affecting a location, time period, or set of impacted entities.
-
D.
floodGauge
Indicates that a device or measurement point is used to monitor and record the level or intensity of flooding at a specific location.
-
E.
floodCause
Indicates that one entity is the cause or source of a flood affecting another entity or area.
- 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_69ad85d5e3008190bdfe0bacdd1f5a1b |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc0defe14819095a337a840e33300 |
completed | March 8, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69adb83810c481909c645c08b978edc1 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:21 p.m.