Triple
T36615292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tryweryn Valley |
E903587
|
entity |
| Predicate | preFloodCommunityType |
P186213
|
FINISHED |
| Object | rural Welsh-speaking community |
—
|
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: rural Welsh-speaking community | Statement: [Tryweryn Valley, preFloodCommunityType, rural Welsh-speaking community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preFloodCommunityType Context triple: [Tryweryn Valley, preFloodCommunityType, rural Welsh-speaking community]
-
A.
floodType
Indicates the specific kind or category of flooding involved in an event or situation.
-
B.
prePartitionCommunity
Indicates a relationship where entities belong to or are associated with the same community as it existed before a specific partition or division event.
-
C.
formerCommunity
Indicates that an entity previously belonged to or was part of a particular community but is no longer a member of it.
-
D.
floodRiskCategory
Indicates the level or classification of flood risk associated with an entity, such as a location or asset.
-
E.
formedByFlooding
Indicates that something came into existence or was created as a result 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_69f76e6960e4819092047756ceb9a17e |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7cabacc1481909e839454ce1057f7 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7c9f4c7c48190ba918d8d5dc8dfd9 |
completed | May 3, 2026, 10:19 p.m. |
Created at: May 3, 2026, 4:11 p.m.