Triple
T25330508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trégor |
E635137
|
entity |
| Predicate | currentLanguageStatus |
P25828
|
FINISHED |
| Object | Breton language endangered |
—
|
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 endangered | Statement: [Trégor, currentLanguageStatus, Breton language endangered]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentLanguageStatus Context triple: [Trégor, currentLanguageStatus, Breton language endangered]
-
A.
currentLanguageSituation
Indicates the language currently being used or in effect in a given context or situation.
-
B.
currentLanguageOfServices
Indicates that a specified language is the one presently used to provide or deliver certain services.
-
C.
hasLanguageStatus
chosen
Indicates that an entity has a particular status or condition regarding its language use, recognition, or classification.
-
D.
languageStatusSource
Indicates the source or authority from which the information about a language’s status is derived.
-
E.
languageOfCurrentAdministration
Indicates the language currently used by the governing or administrative authority in charge.
- 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_69e75a9908108190a95427a97020632a |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 21, 2026, 1:30 p.m.