Triple
T24473572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Léon |
E617167
|
entity |
| Predicate | historicalLanguageAreaOf |
P138140
|
FINISHED |
| Object | Breton language |
—
|
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: Breton language | Statement: [Léon, historicalLanguageAreaOf, Breton language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalLanguageAreaOf Context triple: [Léon, historicalLanguageAreaOf, Breton language]
-
A.
historicalLanguageArea
chosen
Indicates that an entity is located within or associated with a geographic region where a particular language was historically spoken or dominant.
-
B.
historicalLanguageRegion
Indicates that a language was historically spoken or used within a particular geographic region, regardless of its current status there.
-
C.
historicalLanguageOfBearers
Indicates that the specified language is historically spoken or used by the bearers of a given name, title, or designation.
-
D.
historicalLanguageGroup
Indicates that two or more entities belong to the same historically defined language group or family, based on shared linguistic ancestry or development.
-
E.
linguisticArea
Indicates a regional context in which languages share features due to geographic proximity and contact rather than common genetic origin.
- 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_69e2d7f197588190889a03e620558059 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f299457ce081909e8d95fd482928dc |
completed | April 29, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:20 a.m.