Triple
T20606808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belitong Geopark |
E506330
|
entity |
| Predicate | UNESCOGlobalGeoparkDesignationYear |
P138954
|
FINISHED |
| Object | 2021 |
—
|
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: 2021 | Statement: [Belitong Geopark, UNESCOGlobalGeoparkDesignationYear, 2021]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UNESCOGlobalGeoparkDesignationYear Context triple: [Belitong Geopark, UNESCOGlobalGeoparkDesignationYear, 2021]
-
A.
unescoGlobalGeoparkDesignationYear
chosen
Indicates the year in which a site received its official designation as a UNESCO Global Geopark.
-
B.
UNESCOWorldHeritageDesignationYear
Indicates the year in which a site was officially designated as a UNESCO World Heritage site.
-
C.
inscribedOnUNESCOListInYear
Indicates that an entity was officially added to a UNESCO list (such as World Heritage) in a specified year.
-
D.
geoparkNetwork
Indicates that a location or area is part of, associated with, or recognized within a designated geopark network.
-
E.
establishedProtectedAreaYear
Indicates the year in which a protected area was officially established or designated.
- 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_69e0b4bb2b4081908fa4a72444120f35 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aad394e8819080185187a8b3de93 |
completed | April 20, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:41 a.m.