Triple
T12745511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matera |
E304593
|
entity |
| Predicate | culturalDesignationYear |
P963
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [Matera, culturalDesignationYear, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: culturalDesignationYear Context triple: [Matera, culturalDesignationYear, 2019]
-
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.
culturalDesignation
Indicates that an entity has been assigned a particular cultural status, label, or classification within a specific cultural or heritage context.
-
D.
unescoDesignation
Indicates that an entity has been granted a specific designation or status by UNESCO.
-
E.
worldHeritageCulturalExtensionYear
Indicates the year in which a site's existing World Heritage cultural designation was formally extended or expanded.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96406e97c8190b79081039847115c |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:26 p.m.