Triple
T18061261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Room of the Segnatura |
E432178
|
entity |
| Predicate | decorationStart |
P129672
|
FINISHED |
| Object | 1508 |
—
|
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: 1508 | Statement: [Room of the Segnatura, decorationStart, 1508]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decorationStart Context triple: [Room of the Segnatura, decorationStart, 1508]
-
A.
decorationContext
Indicates the situational or environmental setting in which a decoration is used, applied, or intended to be perceived.
-
B.
decorationClass
Indicates that one entity serves as a decorative classification or style category applied to another entity.
-
C.
decorationSystem
Indicates a system or method used to apply, manage, or organize decorative elements in or around an entity.
-
D.
decorationForm
Indicates the specific decorative style, pattern, or motif that characterizes how something is ornamented.
-
E.
decoration
Indicates that one entity serves as an ornament or embellishing element for another entity, enhancing its appearance or style.
- F. None of above. chosen
Provenance (4 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_69d8b9070cac81909fa9473fb1c3f1c7 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4c1066f508190bacf1122e366f87b |
completed | April 19, 2026, 11:48 a.m. |
| PD | Predicate disambiguation | batch_69e3f90c652481908133a73106d78919 |
completed | April 18, 2026, 9:35 p.m. |
| PDg | Predicate description generation | batch_69e42d8eefa88190a700c7c1b4213e46 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:26 a.m.