Triple
T24138412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piazza Grande |
E598153
|
entity |
| Predicate | heritageDesignationBody |
P63420
|
FINISHED |
| Object | UNESCO |
—
|
NE NERFINISHED |
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: UNESCO | Statement: [Piazza Grande, heritageDesignationBody, UNESCO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageDesignationBody Context triple: [Piazza Grande, heritageDesignationBody, UNESCO]
-
A.
heritageDesignation
Indicates that an entity has been formally assigned a specific cultural, historical, or heritage protection status by an authority.
-
B.
heritageDesignationSubject
Indicates that a subject has been assigned a particular heritage designation or status.
-
C.
heritageDesignationSystem
Indicates the formal heritage classification or protection system under which an entity has been designated.
-
D.
heritageDesignationVia
Indicates that a heritage designation for an entity is conferred, recorded, or derived through a specific intermediary process, source, or mechanism.
-
E.
heritageProtectionAuthority
chosen
Indicates that an entity serves as the official body responsible for protecting, managing, or regulating cultural or natural heritage.
- 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_69e288c92e448190ac57034fa0c863ce |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df7e3c20819099ff289789829d7e |
completed | April 29, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:27 p.m.