Triple
T23493394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nivaclé |
E571635
|
entity |
| Predicate | languageVitality |
P152598
|
FINISHED |
| Object | vulnerable |
—
|
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: vulnerable | Statement: [Nivaclé, languageVitality, vulnerable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageVitality Context triple: [Nivaclé, languageVitality, vulnerable]
-
A.
languageDiversity
Indicates the degree to which multiple distinct languages are present and used within a given context or population.
-
B.
linguisticStatusOfArea
Indicates the linguistic status or condition that characterizes a particular geographic area.
-
C.
languageOfSurroundingCulture
Indicates that one entity is the language predominantly used or characteristic of the surrounding culture associated with another entity.
-
D.
languageRevived
Indicates that a previously endangered or no-longer-spoken language has been brought back into active use within a community.
-
E.
ethnicLanguageStatus
Indicates the status or role of a language in relation to a particular ethnic group (e.g., primary, secondary, heritage, or minority language).
- 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_69e245b4829881909b77a70e942bbd54 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7de1ab88190b6c2441c63a99713 |
completed | April 29, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f0bd4a0e408190ad8916faf23562d9 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 17, 2026, 6:05 p.m.