Triple
T25519566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kilombero River |
E639605
|
entity |
| Predicate | floodplainWidth |
P158623
|
FINISHED |
| Object | up to several kilometers |
—
|
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: up to several kilometers | Statement: [Kilombero River, floodplainWidth, up to several kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floodplainWidth Context triple: [Kilombero River, floodplainWidth, up to several kilometers]
-
A.
waterwayWidth
Indicates the measured width of a waterway, typically the distance across it from one bank or edge to the opposite.
-
B.
hasFloodplains
Indicates that an area or region includes land that is subject to flooding, typically adjacent to a river or water body.
-
C.
hasFloodplain
Indicates that an area or location lies within the floodplain associated with a particular water body or flooding source.
-
D.
hasFloodplainType
Indicates that an area or location is associated with a specific type or classification of floodplain.
-
E.
floodGauge
Indicates that a device or measurement point is used to monitor and record the level or intensity of flooding at a specific location.
- F. None of above. chosen
Provenance (4 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_69e75dbe32e48190a62d749a0ff2a96a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f8353d6c81908dd21e9e867d3753 |
completed | May 2, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 2:59 p.m.