Triple
T21571093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Nimba |
E532283
|
entity |
| Predicate | UNESCODangerListSince |
P122939
|
FINISHED |
| Object | 1992 |
—
|
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: 1992 | Statement: [Mount Nimba, UNESCODangerListSince, 1992]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UNESCODangerListSince Context triple: [Mount Nimba, UNESCODangerListSince, 1992]
-
A.
UNESCOEndangermentCategory
Indicates the level of endangerment assigned to a language according to UNESCO’s classification system.
-
B.
addedToListOfWorldHeritageInDanger
Indicates that a site has been officially placed on the List of World Heritage in Danger, recognizing it as threatened and in need of special protection or conservation measures.
-
C.
UNESCOdangerListInscriptionYear
chosen
Indicates the year in which a site was inscribed on UNESCO’s List of World Heritage in Danger.
-
D.
UNESCOListStatus
Indicates that an entity has a specific recognition or classification status in relation to an official UNESCO list.
-
E.
removedFromWorldHeritageInDangerList
Indicates that an entity was taken off the World Heritage in Danger list, signifying it is no longer classified as being under imminent threat.
- 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_69e0c460db088190828c64206a450273 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eee9cc5c448190887a836f577d01ba |
completed | April 27, 2026, 4:45 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:30 p.m.