Triple
T29401299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legune coastal floodplain |
E745648
|
entity |
| Predicate | inundationPattern |
P158858
|
FINISHED |
| Object | flooded during wet 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: flooded during wet season | Statement: [Legune coastal floodplain, inundationPattern, flooded during wet season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inundationPattern Context triple: [Legune coastal floodplain, inundationPattern, flooded during wet season]
-
A.
floodType
Indicates the specific kind or category of flooding involved in an event or situation.
-
B.
floodFrequency
chosen
Indicates how often flooding occurs or is expected to occur at a given location or under specified conditions.
-
C.
floodEvent
Indicates an occurrence of a flooding event affecting a location, time period, or set of impacted entities.
-
D.
inundatedRegion
Indicates that a region is covered or overwhelmed by water, typically due to flooding or heavy precipitation.
-
E.
floodRecord
Indicates that an entity serves as a documented record or report of a flood event affecting another entity or area.
- 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a0772648190b5083f0fa099137c |
completed | May 2, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:51 p.m.