Triple
T3421940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parma Cathedral |
E72132
|
entity |
| Predicate | styleOfInteriorDecoration |
P5509
|
FINISHED |
| Object | Renaissance fresco decoration |
—
|
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: Renaissance fresco decoration | Statement: [Parma Cathedral, styleOfInteriorDecoration, Renaissance fresco decoration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: styleOfInteriorDecoration Context triple: [Parma Cathedral, styleOfInteriorDecoration, Renaissance fresco decoration]
-
A.
interiorStyle
chosen
Indicates that one entity has a particular interior design style or aesthetic characterized by the other entity.
-
B.
decoration
Indicates that one entity serves as an ornament or embellishing element for another entity, enhancing its appearance or style.
-
C.
furnishingType
Indicates the type or category of furnishings associated with an entity, such as a property or room.
-
D.
decorations
Indicates that one entity adds, provides, or serves as ornamental or decorative elements for another entity.
-
E.
interiorFloor
Indicates that one entity is the interior floor surface or flooring of another enclosing space or structure.
- 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_69ad85ad38e48190b7660c5118a35289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb950f65481908c4aad15516e7a7c |
completed | March 8, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69adadfea024819094b41a13bc004bda |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.