Triple
T21571092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Nimba |
E532283
|
entity |
| Predicate | onUNESCODangerList |
P65277
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mount Nimba, onUNESCODangerList, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onUNESCODangerList Context triple: [Mount Nimba, onUNESCODangerList, true]
-
A.
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.
-
B.
inDangerSince
Indicates that an entity has been in a state of danger continuously starting from a specified point in time.
-
C.
UNSafeArea
Indicates that a given area or region is considered dangerous, hazardous, or otherwise not safe for normal use or presence.
-
D.
dangerousWhen
Indicates that one entity becomes harmful, risky, or unsafe under the conditions or in the presence of another entity or situation.
-
E.
reasonForDangerListing
Indicates the specific cause or justification for why something has been classified or listed as dangerous.
- 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.