Triple
T38599992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polesine |
E934182
|
entity |
| Predicate | historicallyFloodProne |
P92510
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Polesine, historicallyFloodProne, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyFloodProne Context triple: [Polesine, historicallyFloodProne, true]
-
A.
historicallyProneTo
chosen
Indicates that an entity has repeatedly or characteristically experienced or exhibited a particular condition, behavior, or event over a significant period in the past.
-
B.
hasFloodRisk
Indicates that an entity is exposed to a potential or expected risk of flooding under certain conditions.
-
C.
hasFloodRiskAreas
Indicates that certain areas are subject to potential flooding or are classified as being at risk of flood events.
-
D.
hasFloodplains
Indicates that an area or region includes land that is subject to flooding, typically adjacent to a river or water body.
-
E.
hasFloodplain
Indicates that an area or location lies within the floodplain associated with a particular water body or flooding source.
- 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a02fc3890a881908b69b0f2d7cc1ce1 |
completed | May 12, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_6a02fb98438c8190938896c00216b9ec |
completed | May 12, 2026, 10:06 a.m. |
Created at: May 3, 2026, 4:32 p.m.