Triple
T22302137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manovo-Gounda St Floris National Park |
E551282
|
entity |
| Predicate | onUNESCODangerListSince |
P65277
|
FINISHED |
| Object | 1997 |
—
|
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: 1997 | Statement: [Manovo-Gounda St Floris National Park, onUNESCODangerListSince, 1997]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onUNESCODangerListSince Context triple: [Manovo-Gounda St Floris National Park, onUNESCODangerListSince, 1997]
-
A.
inDangerSince
Indicates that an entity has been in a state of danger continuously starting from a specified point in time.
-
B.
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.
-
C.
hasUNESCORelation
Indicates a formal relationship or association between an entity and UNESCO, such as recognition, designation, partnership, or program involvement.
-
D.
hasUNCode
Indicates that an entity is associated with a specific United Nations–assigned code that identifies it in UN systems or classifications.
-
E.
isInDanger
Indicates that an entity is exposed to a significant risk of harm, loss, or adverse consequences.
- 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_69e11e46c0188190800181a4233f28fe |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1572517588190bef6f8bfb76afb19 |
completed | April 29, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69e72ffa438481908f80879aef2a589b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:41 p.m.