Triple
T34981718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Gandak River |
E1008831
|
entity |
| Predicate | hasFloodingIssue |
P17084
|
FINISHED |
| Object | seasonal floods in Bihar |
—
|
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: seasonal floods in Bihar | Statement: [Old Gandak River, hasFloodingIssue, seasonal floods in Bihar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFloodingIssue Context triple: [Old Gandak River, hasFloodingIssue, seasonal floods in Bihar]
-
A.
hasFloodHistory
chosen
Indicates that the subject has experienced one or more flood events in the past.
-
B.
reasonForFlooding
Indicates the cause or underlying factor that led to the occurrence of flooding.
-
C.
hasFloodProtectionProject
Indicates that a flood protection project exists or is implemented for the referenced entity.
-
D.
hasFloodControlStructure
Indicates that an entity possesses or is equipped with a structure designed to manage, control, or mitigate flooding.
-
E.
formedByFlooding
Indicates that something came into existence or was created as a result of flooding.
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:01 p.m.