Triple
T22858713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palazzo Zacco |
E566851
|
entity |
| Predicate | hasOrnamentationTheme |
P86416
|
FINISHED |
| Object | grotesque figures |
—
|
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: grotesque figures | Statement: [Palazzo Zacco, hasOrnamentationTheme, grotesque figures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrnamentationTheme Context triple: [Palazzo Zacco, hasOrnamentationTheme, grotesque figures]
-
A.
hasOrnamentation
Indicates that an entity possesses decorative features or embellishments applied to its surface or structure.
-
B.
ornamentationStyle
chosen
Indicates the decorative design or stylistic approach applied as ornamentation to an entity.
-
C.
notableOrnamental
Indicates that something is recognized as a particularly significant or distinguished example of ornamental decoration or design.
-
D.
hasOrchestraType
Indicates that an entity is associated with, or classified by, a specific type or category of orchestra.
-
E.
hasOrchestralFeature
Indicates that something includes, exhibits, or is characterized by a notable orchestral element or component.
- 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_69e24589083081908d5694c4fdc80086 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17ebf1838819092b2b99205a2192f |
completed | April 29, 2026, 3:45 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:37 p.m.