Triple
T36580852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capel Celyn |
E902390
|
entity |
| Predicate | floodingApprovedBy |
P107269
|
FINISHED |
| Object | UK Parliament |
—
|
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: UK Parliament | Statement: [Capel Celyn, floodingApprovedBy, UK Parliament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floodingApprovedBy Context triple: [Capel Celyn, floodingApprovedBy, UK Parliament]
-
A.
formedByFlooding
Indicates that something came into existence or was created as a result of flooding.
-
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.
floodControlProjectAuthorizedBy
chosen
Indicates that a flood control project has been formally approved or sanctioned by a particular authority or organization.
-
D.
isFlooded
Indicates that a location, area, or object is currently covered or overwhelmed by an abnormal amount of water.
-
E.
floodEnhancedBy
Indicates that the occurrence, intensity, or impact of a flood is increased or made more severe by the associated factor or condition.
- 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_69f76e64d8908190868473959a250b94 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.