Triple
T34053834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord of Glyndyfrdwy |
E873299
|
entity |
| Predicate | hasAncestralLandsOf |
P192085
|
FINISHED |
| Object | Owain Glyndŵr |
—
|
NE NERFINISHED |
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: Owain Glyndŵr | Statement: [Lord of Glyndyfrdwy, hasAncestralLandsOf, Owain Glyndŵr]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAncestralLandsOf Context triple: [Lord of Glyndyfrdwy, hasAncestralLandsOf, Owain Glyndŵr]
-
A.
hasAncestralLand
Indicates that an entity possesses land inherited from its ancestors or traditionally associated with its lineage.
-
B.
hasAncestralTerritoriesIn
Indicates that an entity traditionally holds or is associated with ancestral lands located within a specified geographic area.
-
C.
hasAncestralIsland
Indicates that an entity has a specific island from which its ancestors originated or to which its lineage is historically tied.
-
D.
isAncestralVillageOf
Indicates that one place is the original home or traditional village from which another person, family, or community traces its ancestry.
-
E.
hasTribalAncestor
Indicates that an entity is descended from, or has lineage tracing back to, a specified tribal ancestor.
- 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_69f349a3ec2c8190b62da76e54231a0f |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69fcf36bb86c8190a0a0ccf47cb56e5c |
completed | May 7, 2026, 8:17 p.m. |
Created at: May 1, 2026, 1:52 a.m.