Triple
T3966550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Ichkeul |
E92229
|
entity |
| Predicate | addedToWorldHeritageInDangerList |
P16739
|
FINISHED |
| Object | 1996 |
—
|
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: 1996 | Statement: [Lake Ichkeul, addedToWorldHeritageInDangerList, 1996]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addedToWorldHeritageInDangerList Context triple: [Lake Ichkeul, addedToWorldHeritageInDangerList, 1996]
-
A.
addedToListOfWorldHeritageInDanger
chosen
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.
-
B.
heritageThreat
Indicates that an entity poses a risk of damage, loss, or degradation to cultural, historical, or natural heritage.
-
C.
heritageSiteAdvocatedFor
Indicates that an entity actively supports, promotes, or campaigns for the recognition, protection, or preservation of a heritage site.
-
D.
UNESCOEndangermentCategory
Indicates the level of endangerment assigned to a language according to UNESCO’s classification system.
-
E.
unescoDesignation
Indicates that an entity has been granted a specific designation or status by UNESCO.
- 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_69aed96624188190ac8c45bb57ab72b5 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaca33e4819091957c7915857a42 |
completed | March 9, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69aef8f252b081909749d40440d372b2 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:32 p.m.