Triple
T3668525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guddu Barrage |
E77819
|
entity |
| Predicate | helpsProtectFrom |
P20171
|
FINISHED |
| Object | Indus River floods |
—
|
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: Indus River floods | Statement: [Guddu Barrage, helpsProtectFrom, Indus River floods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: helpsProtectFrom Context triple: [Guddu Barrage, helpsProtectFrom, Indus River floods]
-
A.
protects
Indicates taking action to keep someone or something safe from harm, danger, or negative effects.
-
B.
providesProtectionAgainst
chosen
Indicates that one entity serves to guard, shield, or defend another entity from a specified harm, threat, or adverse effect.
-
C.
helpedSecure
Indicates that one entity contributed to obtaining, protecting, or ensuring the safety or stability of another entity or outcome.
-
D.
protectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
E.
aimsToProtect
Indicates an intention or purpose to safeguard or defend one entity, value, or condition from harm, risk, or undesirable outcomes.
- 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_69ad85e083008190b2e1b7085fe500bd |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc42997d88190bc765559bd7645fc |
completed | March 8, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69adb84a20288190a092e4a1b045fe3f |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:25 p.m.