Triple
T35242989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hezhen people |
E1017576
|
entity |
| Predicate | threatStatusOfLanguage |
P27859
|
FINISHED |
| Object | 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: endangered | Statement: [Hezhen people, threatStatusOfLanguage, endangered]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threatStatusOfLanguage Context triple: [Hezhen people, threatStatusOfLanguage, endangered]
-
A.
threatStatus
chosen
Indicates the level or category of risk or danger posed by one entity to another or to a defined system or environment.
-
B.
threatStatusSystem
Indicates the classification framework or system used to assign a conservation or threat status to an entity.
-
C.
threatContext
Indicates the situational conditions, factors, or environment in which a threat occurs or is relevant.
-
D.
threatCategory
Indicates the classification of a threat according to its type, severity, or nature within a defined risk or security framework.
-
E.
languageEndangermentFactors
Indicates the various social, political, economic, and cultural conditions that contribute to a language becoming vulnerable, endangered, or extinct.
- 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_69f76de235048190b990070c23c51b6b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.