Triple
T24676466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Logone floodplain |
E610998
|
entity |
| Predicate | floodingPeriod |
P13044
|
FINISHED |
| Object | rainy season |
—
|
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: rainy season | Statement: [Logone floodplain, floodingPeriod, rainy season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floodingPeriod Context triple: [Logone floodplain, floodingPeriod, rainy season]
-
A.
floodRecord
Indicates that an entity serves as a documented record or report of a flood event affecting another entity or area.
-
B.
floodEvent
Indicates an occurrence of a flooding event affecting a location, time period, or set of impacted entities.
-
C.
hasSeasonalFlooding
chosen
Indicates that an area regularly experiences flooding during specific, recurring times of the year.
-
D.
floodedFor
Indicates that one entity is intentionally inundated or submerged with water (or another liquid) for the benefit, use, or purpose of another entity.
-
E.
floodType
Indicates the specific kind or category of flooding involved in an event or situation.
- 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_69e2c4d5c2dc8190ac857dea25ec6ce9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 3:05 a.m.