Triple
T8670893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Langkawi Archipelago |
E205791
|
entity |
| Predicate | UNESCOStatusYear |
P963
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [Langkawi Archipelago, UNESCOStatusYear, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UNESCOStatusYear Context triple: [Langkawi Archipelago, UNESCOStatusYear, 2007]
-
A.
inscribedOnUNESCOListInYear
Indicates that an entity was officially added to a UNESCO list (such as World Heritage) in a specified year.
-
B.
UNESCOListStatus
Indicates that an entity has a specific recognition or classification status in relation to an official UNESCO list.
-
C.
UNESCOWorldHeritageExtensionYear
Indicates the year in which an existing UNESCO World Heritage Site was officially extended or had its boundaries/inscription scope modified.
-
D.
UNESCOWorldHeritageDesignationYear
chosen
Indicates the year in which a site was officially designated as a UNESCO World Heritage site.
-
E.
UNESCOSessionOfInscription
Indicates the specific UNESCO session during which an item was formally inscribed or added to a UNESCO list.
- 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_69ca83529a9c8190b5c075b4f14636ed |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4918e3a88190b3c49043211840fd |
completed | March 31, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cc4564e018819081036722f3e42a71 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:31 p.m.