Triple
T11732831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khagaria district |
E278940
|
entity |
| Predicate | highFloodRisk |
P58564
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Khagaria district, highFloodRisk, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highFloodRisk Context triple: [Khagaria district, highFloodRisk, true]
-
A.
hasFloodRisk
Indicates that an entity is exposed to a potential or expected risk of flooding under certain conditions.
-
B.
floodRiskCategory
chosen
Indicates the level or classification of flood risk associated with an entity, such as a location or asset.
-
C.
floodStage
Indicates that a water body’s level has reached or exceeded the defined height at which flooding is expected to begin or become hazardous.
-
D.
floodEvent
Indicates an occurrence of a flooding event affecting a location, time period, or set of impacted entities.
-
E.
shareFloodRisk
Indicates that two or more entities are exposed to the same or overlapping risk 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4daa7f48190896fc7653e9dd70b |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7f51248190bf492bd7509b5413 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.