Triple
T15016970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jabal Moussa Biosphere Reserve |
E377981
|
entity |
| Predicate | yearOfUNESCODesignation |
P105575
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [Jabal Moussa Biosphere Reserve, yearOfUNESCODesignation, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfUNESCODesignation Context triple: [Jabal Moussa Biosphere Reserve, yearOfUNESCODesignation, 2009]
-
A.
inscribedOnUNESCOListInYear
Indicates that an entity was officially added to a UNESCO list (such as World Heritage) in a specified year.
-
B.
UNESCOTransferYear
Indicates the year in which responsibility, ownership, or designation of something was formally transferred under the authority or framework of UNESCO.
-
C.
UNESCOWorldHeritageDesignationYear
Indicates the year in which a site was officially designated as a UNESCO World Heritage site.
-
D.
unescoDesignation
Indicates that an entity has been granted a specific designation or status by UNESCO.
-
E.
yearDesignated
chosen
Indicates the specific year in which something was formally designated, assigned, or given an official status.
- 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7633fcc8190b2231f43252bc46f |
completed | April 15, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69de9a67cbc481909c19c2de57de4eb7 |
completed | April 14, 2026, 7:50 p.m. |
Created at: April 10, 2026, 2:55 a.m.