Triple
T31811815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Speicherstadt |
E812029
|
entity |
| Predicate | UNESCOInscriptionDate |
P57323
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [Speicherstadt, UNESCOInscriptionDate, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UNESCOInscriptionDate Context triple: [Speicherstadt, UNESCOInscriptionDate, 2015]
-
A.
UNESCOInscribedBy
Indicates that a site, object, or element has been formally inscribed or designated by UNESCO, typically on one of its official heritage or recognition lists.
-
B.
inscribedOnUNESCOListInYear
chosen
Indicates that an entity was officially added to a UNESCO list (such as World Heritage) in a specified year.
-
C.
yearOfUNESCORecognition
Indicates the specific year in which something was officially recognized or inscribed by UNESCO.
-
D.
UNESCOWorldHeritageDesignationYear
Indicates the year in which a site was officially designated as a UNESCO World Heritage site.
-
E.
UNESCOSerialNomination
Indicates that multiple geographically or culturally related sites are jointly nominated as a single serial property on the UNESCO World Heritage 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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 30, 2026, 11:43 p.m.