Triple
T36580853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capel Celyn |
E902390
|
entity |
| Predicate | floodingOpposedBy |
P186050
|
FINISHED |
| Object | Welsh people |
—
|
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: Welsh people | Statement: [Capel Celyn, floodingOpposedBy, Welsh people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floodingOpposedBy Context triple: [Capel Celyn, floodingOpposedBy, Welsh people]
-
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.
floodEnhancedBy
Indicates that the occurrence, intensity, or impact of a flood is increased or made more severe by the associated factor or condition.
-
D.
floodCause
Indicates that one entity is the cause or source of a flood affecting another entity or area.
-
E.
floodConsequence
Indicates the resulting effects, outcomes, or impacts that occur as a consequence of a flood event.
- 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.