Triple
T12116047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Welsh people |
E288563
|
entity |
| Predicate | hasEndonymLanguageName |
P1435
|
FINISHED |
| Object | Cymraeg |
—
|
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: Cymraeg | Statement: [Welsh people, hasEndonymLanguageName, Cymraeg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEndonymLanguageName Context triple: [Welsh people, hasEndonymLanguageName, Cymraeg]
-
A.
hasEndonymLanguage
Indicates that the language specified is the one in which a name or term is expressed in its own native or local form.
-
B.
hasEndonym
chosen
Indicates that an entity has a name or designation used by native speakers or within its own local language or community.
-
C.
hasEndonymType
Indicates the specific type or category of an entity’s endonym (its name in its own language or local usage).
-
D.
isEndonym
Indicates that a name is used by a group to refer to themselves or their own place/language, rather than being an external or foreign designation.
-
E.
hasNameInLocalLanguage
Indicates that an entity is associated with a name expressed in the local or native language of a given context or region.
- 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_69d6ab4a5c448190a110d1273314b21a |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9164ada5081908676bd9e5947268a |
completed | April 10, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69d9150497408190921334d21503375a |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:49 p.m.