Triple
T31816224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khinalug |
E812139
|
entity |
| Predicate | localLanguageStatus |
P176357
|
FINISHED |
| Object | endangered 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: endangered language | Statement: [Khinalug, localLanguageStatus, endangered language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localLanguageStatus Context triple: [Khinalug, localLanguageStatus, endangered language]
-
A.
currentLanguageSituation
Indicates the language currently being used or in effect in a given context or situation.
-
B.
languageStatusSource
Indicates the source or authority from which the information about a language’s status is derived.
-
C.
localLanguageName
Indicates the name of a language as it is written or referred to in its own local or native form.
-
D.
ethnicLanguageStatus
Indicates the status or role of a language in relation to a particular ethnic group (e.g., primary, secondary, heritage, or minority language).
-
E.
nationalLanguageStatus
Indicates that a language holds official or nationally recognized status within a country or political entity.
- F. None of above. chosen
Provenance (4 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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6e029f0f88190b1f88d82a4a2cabd |
completed | May 3, 2026, 5:42 a.m. |
Created at: April 30, 2026, 11:44 p.m.