Triple
T31398632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parāčī |
E800930
|
entity |
| Predicate | statusInUNESCOAtlas |
P63304
|
FINISHED |
| Object | definitely endangered |
—
|
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: definitely endangered | Statement: [Parāčī, statusInUNESCOAtlas, definitely endangered]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInUNESCOAtlas Context triple: [Parāčī, statusInUNESCOAtlas, definitely endangered]
-
A.
UNESCOListStatus
chosen
Indicates that an entity has a specific recognition or classification status in relation to an official UNESCO list.
-
B.
naturalHeritageStatus
Indicates the official conservation or protection designation assigned to a natural site or feature based on its environmental, ecological, or heritage value.
-
C.
unescoDesignation
Indicates that an entity has been granted a specific designation or status by UNESCO.
-
D.
hasUNESCOCandidateSite
Indicates that an entity possesses or includes at least one site that is a candidate for inscription on the UNESCO World Heritage List.
-
E.
UNESCOdangerListInscriptionYear
Indicates the year in which a site was inscribed on UNESCO’s List of World Heritage in Danger.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69fe5c1a502081909d4024e514309c8e |
completed | May 8, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69fe5a9df21c819087153f5d0bcaa987 |
completed | May 8, 2026, 9:50 p.m. |
Created at: April 29, 2026, 9:19 p.m.