Triple
T7684235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liabuku language |
E174072
|
entity |
| Predicate | possibleEndangermentStatus |
P65277
|
FINISHED |
| Object | endangered language |
—
|
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 language | Statement: [Liabuku language, possibleEndangermentStatus, endangered language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleEndangermentStatus Context triple: [Liabuku language, possibleEndangermentStatus, endangered language]
-
A.
endangerment
Indicates a relationship in which one entity exposes another to potential harm, risk, or danger.
-
B.
dangerousWhen
Indicates that one entity becomes harmful, risky, or unsafe under the conditions or in the presence of another entity or situation.
-
C.
inDangerSince
Indicates that an entity has been in a state of danger continuously starting from a specified point in time.
-
D.
underDangerList
chosen
Indicates that an entity is classified as being on a designated danger or endangered list, signifying it is at risk or under threat.
-
E.
threatStatus
Indicates the level or category of risk or danger posed by one entity to another or to a defined system or environment.
- 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_69c6995840408190a19de6c51090f46f |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7048b0b448190889bd40e0a38e51a |
completed | March 27, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69c701618d3481908be84b76f36ac5a1 |
completed | March 27, 2026, 10:14 p.m. |
Created at: March 27, 2026, 4:01 p.m.