Triple
T16535800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Llanwddyn |
E401685
|
entity |
| Predicate | hasOriginalSiteStatus |
P62853
|
FINISHED |
| Object | submerged under Lake Vyrnwy |
—
|
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: submerged under Lake Vyrnwy | Statement: [Llanwddyn, hasOriginalSiteStatus, submerged under Lake Vyrnwy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalSiteStatus Context triple: [Llanwddyn, hasOriginalSiteStatus, submerged under Lake Vyrnwy]
-
A.
hasSiteStatusAtStart
Indicates that an entity possesses a particular site status at the beginning of a specified period or event.
-
B.
hasSiteStatus
Indicates the current operational or condition status assigned to a particular site.
-
C.
originalLocationStatus
chosen
Indicates the status or condition of an entity’s original location, such as whether it remains, has changed, or is otherwise affected.
-
D.
hasOriginalVersion
Indicates that one entity is the original or initial version from which another entity is derived or adapted.
-
E.
originalSiteUse
Indicates the historical or initial functional use or purpose assigned to a particular site before any subsequent changes or developments.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e345574d88819094548367bf983078 |
completed | April 18, 2026, 8:48 a.m. |
| PD | Predicate disambiguation | batch_69e2969fab208190ad64164d24748c45 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:15 a.m.