Triple
T36580849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capel Celyn |
E902390
|
entity |
| Predicate | wasFloodedBy |
P186049
|
FINISHED |
| Object | Liverpool Corporation |
—
|
NE NERFINISHED |
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: Liverpool Corporation | Statement: [Capel Celyn, wasFloodedBy, Liverpool Corporation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFloodedBy Context triple: [Capel Celyn, wasFloodedBy, Liverpool Corporation]
-
A.
isFlooded
Indicates that a location, area, or object is currently covered or overwhelmed by an abnormal amount of water.
-
B.
floodedFor
Indicates that one entity is intentionally inundated or submerged with water (or another liquid) for the benefit, use, or purpose of another entity.
-
C.
formedByFlooding
Indicates that something came into existence or was created as a result of flooding.
-
D.
hasFloodHistory
Indicates that the subject has experienced one or more flood events in the past.
-
E.
reasonForFlooding
Indicates the cause or underlying factor that led to the occurrence of flooding.
- 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_69f76e64d8908190868473959a250b94 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 3, 2026, 4:11 p.m.