Triple
T32433826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ystwyth Valley |
E828801
|
entity |
| Predicate | scenicDesignationStatus |
P174081
|
FINISHED |
| Object | locally valued landscape |
—
|
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: locally valued landscape | Statement: [Ystwyth Valley, scenicDesignationStatus, locally valued landscape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scenicDesignationStatus Context triple: [Ystwyth Valley, scenicDesignationStatus, locally valued landscape]
-
A.
stateDesignation
Indicates that an entity has been formally assigned or recognized with a particular status, title, or classification by an official authority or governing body.
-
B.
hasScenicDesignationSince
Indicates that an entity has held an official scenic designation continuously since a specified date.
-
C.
environmentDesignation
Indicates that an entity is assigned a specific environmental classification or status within a given context.
-
D.
religiousDesignation
Indicates the specific religious role, status, or affiliation assigned to an entity.
-
E.
landmarkDesignationLevel
Indicates the specific level or category of official landmark status that has been assigned to an entity.
- 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_69f3491bf298819097b610f772d54a6d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2b0108c81908aab3d55aaf9f8e5 |
completed | May 3, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bb344bb48190a8089f29c0063ded |
completed | May 3, 2026, 3:04 a.m. |
Created at: May 1, 2026, 12:55 a.m.