Triple
T24981953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dogon Country |
E625191
|
entity |
| Predicate | unescoWorldHeritageYear |
P963
|
FINISHED |
| Object | 1989 |
—
|
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: 1989 | Statement: [Dogon Country, unescoWorldHeritageYear, 1989]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unescoWorldHeritageYear Context triple: [Dogon Country, unescoWorldHeritageYear, 1989]
-
A.
worldHeritageCulturalExtensionYear
Indicates the year in which a site's existing World Heritage cultural designation was formally extended or expanded.
-
B.
UNESCOWorldHeritageExtensionYear
Indicates the year in which an existing UNESCO World Heritage Site was officially extended or had its boundaries/inscription scope modified.
-
C.
yearOfUNESCORecognition
Indicates the specific year in which something was officially recognized or inscribed by UNESCO.
-
D.
UNESCOTransferYear
Indicates the year in which responsibility, ownership, or designation of something was formally transferred under the authority or framework of UNESCO.
-
E.
UNESCOWorldHeritageDesignationYear
chosen
Indicates the year in which a site was officially designated as a UNESCO World Heritage site.
- 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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 18, 2026, 6:02 a.m.