Triple
T11468891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valaisan Arpitan |
E271849
|
entity |
| Predicate | endangermentTrend |
P35362
|
FINISHED |
| Object | declining number of speakers |
—
|
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: declining number of speakers | Statement: [Valaisan Arpitan, endangermentTrend, declining number of speakers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endangermentTrend Context triple: [Valaisan Arpitan, endangermentTrend, declining number of speakers]
-
A.
endangerment
Indicates a relationship in which one entity exposes another to potential harm, risk, or danger.
-
B.
conservationStatusTrend
chosen
Indicates the direction or pattern of change over time in the conservation status of an entity (e.g., improving, stable, or declining).
-
C.
threatenedBy
Indicates that one entity poses a danger or potential harm to another entity.
-
D.
areEndangeredIn
Indicates that the entities are classified as endangered within a specified geographic area or jurisdiction.
-
E.
areEndangeredOrVulnerable
Indicates that the entities are classified as being at risk of extinction, either endangered or vulnerable, according to conservation status criteria.
- 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d82949e3688190b024a4980666c94f |
completed | April 9, 2026, 10:33 p.m. |
| PD | Predicate disambiguation | batch_69d8086ecd6c81908f424864857762d6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:35 p.m.