Triple
T25839249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bolzano Cathedral |
E650887
|
entity |
| Predicate | roofPattern |
P3576
|
FINISHED |
| Object | geometric colored pattern |
—
|
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: geometric colored pattern | Statement: [Bolzano Cathedral, roofPattern, geometric colored pattern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roofPattern Context triple: [Bolzano Cathedral, roofPattern, geometric colored pattern]
-
A.
roofPatternInspiredBy
Indicates that the design or arrangement of a roof follows or is derived from a particular pattern, style, or source of inspiration.
-
B.
hasPavementPattern
Indicates that an entity possesses or is characterized by a specific pattern or design in its pavement surface.
-
C.
glazingPattern
Indicates the arrangement or design pattern of glazing elements (such as panes or glass sections) within a structure or object.
-
D.
airingPattern
Indicates the recurring schedule or pattern according to which something (such as a program or content) is broadcast or made available.
-
E.
roofFeature
chosen
Indicates that one entity is a feature, element, or characteristic that is part of or associated with a roof.
- 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_69e7ab38086081908f3a8e7e0c6efd83 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f601f80b9c8190947c4542654455a6 |
completed | May 2, 2026, 1:54 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 7:49 a.m.