Triple
T2309282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Na-Dene |
E51913
|
entity |
| Predicate | includesEndangeredLanguages |
P39119
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Na-Dene, includesEndangeredLanguages, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesEndangeredLanguages Context triple: [Na-Dene, includesEndangeredLanguages, true]
-
A.
languageEndangermentStatus
Indicates the degree to which a language is at risk of falling out of use or becoming extinct.
-
B.
hasLanguageRevitalizationEfforts
Indicates that there are organized actions or initiatives aimed at preserving, strengthening, or reviving the use of a particular language.
-
C.
extantLanguage
Indicates that a language currently exists or is in active use, as opposed to being extinct or only historically attested.
-
D.
areEndangeredIn
Indicates that the entities are classified as endangered within a specified geographic area or jurisdiction.
-
E.
languageDiversity
Indicates the degree to which multiple distinct languages are present and used within a given context or population.
- 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_69a88b0bb30c81908ded03b006d29387 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abce1f4f0c8190a714e4dcb8449f7e |
completed | March 7, 2026, 7:05 a.m. |
| PD | Predicate disambiguation | batch_69abc58ce2a081908ce2f0cadd92e9f8 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abce1e7c788190a15890feb2437f1d |
completed | March 7, 2026, 7:05 a.m. |
Created at: March 4, 2026, 7:49 p.m.