Triple
T4761409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kutenai language |
E105705
|
entity |
| Predicate | endangermentLevel |
P3842
|
FINISHED |
| Object | severely 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: severely endangered | Statement: [Kutenai language, endangermentLevel, severely endangered]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endangermentLevel Context triple: [Kutenai language, endangermentLevel, severely endangered]
-
A.
endangerment
Indicates a relationship in which one entity exposes another to potential harm, risk, or danger.
-
B.
threatenedBy
Indicates that one entity poses a danger or potential harm to another entity.
-
C.
hasEmergencyLevel
Indicates that an entity is associated with a specific degree or severity of emergency status.
-
D.
riskLevel
chosen
Indicates the degree of potential harm, loss, or adverse outcome associated with a particular situation, action, or entity.
-
E.
areEndangeredIn
Indicates that the entities are classified as endangered within a specified geographic area or jurisdiction.
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650eefe08190b99f9f01b121dbfd |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd6225c9488190afee5bb3619d0365 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.