Triple
T22020066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gower |
E543819
|
entity |
| Predicate | hasLanguage |
P15
|
FINISHED |
| Object | Welsh |
—
|
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: Welsh | Statement: [Gower, hasLanguage, Welsh]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Welsh Context triple: [Gower, hasLanguage, Welsh]
-
A.
Welsh
chosen
Welsh is a Celtic language native to Wales, known for its rich literary tradition and status as one of the oldest living languages in Europe.
-
B.
Italian Welsh
Italian Welsh are people of Italian descent living in Wales, forming a distinct subgroup within the broader Italian community in the United Kingdom.
-
C.
Old Welsh
Old Welsh is the earliest documented stage of the Welsh language, attested in early medieval Britain and forming the linguistic ancestor of Middle and Modern Welsh.
-
D.
Kernewek Kemmyn
Kernewek Kemmyn is a standardized orthography of revived Cornish designed in the late 20th century to provide a more phonemic and consistent spelling system for the language.
-
E.
Cornish
Cornish is a revived Southwestern Brittonic Celtic language historically spoken in Cornwall, England.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e2e8ea4819084210fe06d3a1b8d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127c6b5fc8190bc49ddb058f28a44 |
completed | April 28, 2026, 9:33 p.m. |
Created at: April 16, 2026, 8:23 p.m.