Triple
T24732920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yavitero |
E618334
|
entity |
| Predicate | isEndangeredLanguage |
P105864
|
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: [Yavitero, isEndangeredLanguage, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEndangeredLanguage Context triple: [Yavitero, isEndangeredLanguage, true]
-
A.
endangeredLanguage
chosen
Indicates that a language is at risk of falling out of use and potentially becoming extinct due to having too few active speakers or insufficient intergenerational transmission.
-
B.
languageEndangermentStatus
Indicates the degree to which a language is at risk of falling out of use or becoming extinct.
-
C.
includesEndangeredLanguages
Indicates that the subject contains, encompasses, or otherwise involves one or more languages classified as endangered.
-
D.
extinctionOfLanguage
Indicates the event or process by which a language ceases to be spoken or used by any living community.
-
E.
endangeredLanguageFamily
Indicates that a language family is at risk of losing its member languages due to declining numbers of speakers or transmission.
- 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_69e2fab772608190b74163751047ff50 |
completed | April 18, 2026, 3:29 a.m. |
| NER | Named-entity recognition | batch_69f410fe3b848190ae296a29f742ee30 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ee8ada8819089a7016b50308ff0 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:02 a.m.