Triple
T16535801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Llanwddyn |
E401685
|
entity |
| Predicate | hasRelocatedVillage |
P1660
|
FINISHED |
| Object | present-day Llanwddyn above reservoir |
—
|
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: present-day Llanwddyn above reservoir | Statement: [Llanwddyn, hasRelocatedVillage, present-day Llanwddyn above reservoir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelocatedVillage Context triple: [Llanwddyn, hasRelocatedVillage, present-day Llanwddyn above reservoir]
-
A.
hasVillage
Indicates that an entity possesses, contains, or is associated with a village.
-
B.
hasRelocatedTemple
Indicates that a temple has been moved from its original location to a new site.
-
C.
relocatedWithin
Indicates that an entity has moved from one location to another while remaining within the same broader area or jurisdiction.
-
D.
relocatedTo
chosen
Indicates that an entity has moved or been transferred from its previous location to a new specified location.
-
E.
relocatedDuring
Indicates that an entity changed its location or place of residence within the time span of a specified event or period.
- 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.