Triple
T33324000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maes Gwyddno |
E853215
|
entity |
| Predicate | rulerInLegend |
P134527
|
FINISHED |
| Object | Gwyddno Garanhir |
—
|
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: Gwyddno Garanhir | Statement: [Maes Gwyddno, rulerInLegend, Gwyddno Garanhir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rulerInLegend Context triple: [Maes Gwyddno, rulerInLegend, Gwyddno Garanhir]
-
A.
recognizedAsRuler
Indicates that one entity is acknowledged or accepted by others as the legitimate ruler or sovereign authority.
-
B.
rulerDepicted
Indicates that a depicted figure in a representation is the ruler (or sovereign authority) associated with that context or scene.
-
C.
regionOfLegend
Indicates the geographic area or locale with which a particular legend or myth is associated.
-
D.
inLegendRole
chosen
Indicates that an entity appears in a legendary or mythic context fulfilling a specific narrative or symbolic role.
-
E.
involvesRuler
Indicates that the relationship or action includes or pertains to a ruler as a participating party.
- 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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:33 a.m.