Triple
T14458057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santa Maria in Domnica |
E358505
|
entity |
| Predicate | hasApseDecoration |
P38145
|
FINISHED |
| Object | 9th-century mosaic cycle |
—
|
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: 9th-century mosaic cycle | Statement: [Santa Maria in Domnica, hasApseDecoration, 9th-century mosaic cycle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApseDecoration Context triple: [Santa Maria in Domnica, hasApseDecoration, 9th-century mosaic cycle]
-
A.
hasApse
Indicates that a structure or building possesses an apse, typically a semicircular or polygonal recess, as one of its architectural features.
-
B.
hasDecor
chosen
Indicates that one entity possesses, features, or is adorned with a particular decorative element or style.
-
C.
hasCeilingDecoration
Indicates that an entity features or is adorned with a decorative element on its ceiling.
-
D.
hasDomeDecoration
Indicates that an entity’s dome is adorned with specific decorative elements or ornamentation.
-
E.
usesTraditionalDecoration
Indicates that an entity employs customary or historically established decorative styles or motifs in its design or presentation.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91aabebc819097eb61b2d81c9a91 |
completed | April 14, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69de5c42bd3c81909a62acf30cc24d1e |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:19 a.m.