Triple
T33432684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copper Coast |
E856171
|
entity |
| Predicate | UNESCOGlobalGeoparkSince |
P138954
|
FINISHED |
| Object | 2004 |
—
|
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: 2004 | Statement: [Copper Coast, UNESCOGlobalGeoparkSince, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UNESCOGlobalGeoparkSince Context triple: [Copper Coast, UNESCOGlobalGeoparkSince, 2004]
-
A.
unescoGlobalGeoparkDesignationYear
chosen
Indicates the year in which a site received its official designation as a UNESCO Global Geopark.
-
B.
UNESCOBiosphereReserveSince
Indicates that an area has held the official status of a UNESCO Biosphere Reserve starting from a specified point in time.
-
C.
geoparkNetwork
Indicates that a location or area is part of, associated with, or recognized within a designated geopark network.
-
D.
hasUNESCOBiosphereReserve
Indicates that an entity includes, contains, or is associated with a designated UNESCO Biosphere Reserve.
-
E.
UNESCOWorldHeritageSiteWithin
Indicates that a UNESCO World Heritage Site is geographically located within the boundaries of a specified area or region.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:36 a.m.