Triple
T821461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amur River |
E17754
|
entity |
| Predicate | hasFloods |
P13044
|
FINISHED |
| Object | summer |
—
|
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: summer | Statement: [Amur River, hasFloods, summer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFloods Context triple: [Amur River, hasFloods, summer]
-
A.
hasFloodRisk
Indicates that an entity is exposed to a potential or expected risk of flooding under certain conditions.
-
B.
hasSeasonalFlooding
chosen
Indicates that an area regularly experiences flooding during specific, recurring times of the year.
-
C.
hasFloodHistory
Indicates that the subject has experienced one or more flood events in the past.
-
D.
hasFloodplain
Indicates that an area or location lies within the floodplain associated with a particular water body or flooding source.
-
E.
hasRiverActivity
Indicates that an entity engages in, supports, or is associated with activities occurring on or along a river.
- 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_69a4937bcaac8190a322524ac6f45a5a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ab976094819086d676404d745750 |
completed | March 1, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69a4aa76a7808190ac7fd9ba1a4cebcb |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.