Triple
T14789686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bunge Land |
E347618
|
entity |
| Predicate | floodingCharacteristic |
P25274
|
FINISHED |
| Object | periodically flooded by the sea |
—
|
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: periodically flooded by the sea | Statement: [Bunge Land, floodingCharacteristic, periodically flooded by the sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floodingCharacteristic Context triple: [Bunge Land, floodingCharacteristic, periodically flooded by the sea]
-
A.
floodType
Indicates the specific kind or category of flooding involved in an event or situation.
-
B.
hydrologicalCharacteristic
chosen
Indicates a relationship where a hydrological feature or condition (such as water flow, level, or behavior) characterizes or describes another entity.
-
C.
floodEvent
Indicates an occurrence of a flooding event affecting a location, time period, or set of impacted entities.
-
D.
floodCause
Indicates that one entity is the cause or source of a flood affecting another entity or area.
-
E.
hasSeasonalFlooding
Indicates that an area regularly experiences flooding during specific, recurring times of the year.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decaa1e9ec81908d7c26c1c4e43014 |
completed | April 14, 2026, 11:15 p.m. |
| PD | Predicate disambiguation | batch_69de8c090d1081909b5a9bf437499d6c |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.