Triple
T12468797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proto-Brythonic |
E297998
|
entity |
| Predicate | phonologicalChangeFrom |
P40496
|
FINISHED |
| Object | Proto-Celtic loss of final syllables |
—
|
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: Proto-Celtic loss of final syllables | Statement: [Proto-Brythonic, phonologicalChangeFrom, Proto-Celtic loss of final syllables]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: phonologicalChangeFrom Context triple: [Proto-Brythonic, phonologicalChangeFrom, Proto-Celtic loss of final syllables]
-
A.
hasPhonologicalChange
Indicates a relationship where one linguistic form undergoes a change in its sound structure relative to another form or earlier state.
-
B.
hasPhonologicalBasisFor
chosen
Indicates that one entity serves as the phonological source, motivation, or foundation for another entity.
-
C.
hasPronunciationDifferenceFrom
Indicates that two linguistic items differ in how they are pronounced.
-
D.
languageReform
Indicates efforts or actions aimed at changing, standardizing, or improving aspects of a language, such as its spelling, grammar, or usage rules.
-
E.
changedFrom
Indicates that an entity previously had one state, value, or form and was altered or updated from that prior condition to a new one.
- 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_69d6ada270808190b1a2b2e7b02bb426 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e626dbc8190ac7dcdb542ba9b0c |
completed | April 10, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69d94d3f701c81909dd0e00251ac8553 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:56 p.m.