Triple
T36862032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kosi river region |
E910967
|
entity |
| Predicate | riverBehavior |
P58508
|
FINISHED |
| Object | frequent avulsions |
—
|
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 avulsions | Statement: [Kosi river region, riverBehavior, frequent avulsions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverBehavior Context triple: [Kosi river region, riverBehavior, frequent avulsions]
-
A.
riverPhenomenon
chosen
Indicates a natural event, condition, or process that occurs in or directly affects a river.
-
B.
raceRiver
Indicates that an entity participates in a race that takes place on or along a river.
-
C.
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).
-
D.
riverFeatureType
Indicates the specific kind or category of physical or functional feature associated with a river (e.g., source, mouth, tributary, channel segment).
-
E.
surfaceWaterBehavior
Indicates how surface water behaves or changes under certain conditions or over time.
- 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_69f76e80f6f0819091cba8e19b269615 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:13 p.m.