Triple
T18679464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sistine Chapel of the East |
E456692
|
entity |
| Predicate | hasDecorationTechnique |
P3047
|
FINISHED |
| Object | fresco painting |
—
|
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: fresco painting | Statement: [Sistine Chapel of the East, hasDecorationTechnique, fresco painting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDecorationTechnique Context triple: [Sistine Chapel of the East, hasDecorationTechnique, fresco painting]
-
A.
hasTechnique
chosen
Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
-
B.
hasDecor
Indicates that one entity possesses, features, or is adorned with a particular decorative element or style.
-
C.
containsDecorationFrom
Indicates that one entity includes or incorporates a decorative element that originates from another entity.
-
D.
typeOfDecoration
Indicates the specific kind or style of decoration associated with an entity or applied in a given context.
-
E.
hasArtFeature
Indicates that an entity possesses or is characterized by a particular artistic attribute, element, or stylistic feature.
- 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e55b2783648190bb602e2b07eedf92 |
completed | April 19, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:48 a.m.