Triple
T20534134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lamu |
E504148
|
entity |
| Predicate | heritageYearInscribed |
P963
|
FINISHED |
| Object | 2001 |
—
|
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: 2001 | Statement: [Lamu, heritageYearInscribed, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageYearInscribed Context triple: [Lamu, heritageYearInscribed, 2001]
-
A.
inscribedOnUNESCOListInYear
Indicates that an entity was officially added to a UNESCO list (such as World Heritage) in a specified year.
-
B.
UNESCOWorldHeritageDesignationYear
chosen
Indicates the year in which a site was officially designated as a UNESCO World Heritage site.
-
C.
UNESCOWorldHeritageExtensionYear
Indicates the year in which an existing UNESCO World Heritage Site was officially extended or had its boundaries/inscription scope modified.
-
D.
heritageRevelationYear
Indicates the year in which a particular heritage status, designation, or significance was formally revealed, recognized, or made public.
-
E.
UNESCOTransferYear
Indicates the year in which responsibility, ownership, or designation of something was formally transferred under the authority or framework of UNESCO.
- 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_69e0b4b476648190bc6019622ae54d3c |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a06df04081908fa95c6214f06093 |
completed | April 20, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69e59fe5592c8190bb6122b784496d02 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:37 a.m.