Triple
T16215897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of Santi Bonifacio e Alessio |
E393590
|
entity |
| Predicate | hasBaroqueInterior |
P6655
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Church of Santi Bonifacio e Alessio, hasBaroqueInterior, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBaroqueInterior Context triple: [Church of Santi Bonifacio e Alessio, hasBaroqueInterior, true]
-
A.
hasRichInteriorDecoration
Indicates that an entity features elaborate, ornate, or luxuriously detailed interior decoration.
-
B.
hasAltarpiecesInStyle
Indicates that an entity possesses or features altarpieces that are created or designed in a specified artistic style.
-
C.
hasInteriorFeature
chosen
Indicates that an entity contains or includes a specific feature within its interior space.
-
D.
baroqueArchitect
Indicates that one entity is an architect who works in, is associated with, or is characterized by the Baroque architectural style in relation to another entity.
-
E.
hasMainAltarpiece
Indicates that an entity (typically a religious building or space) possesses a specific artwork or structure serving as its principal altarpiece.
- 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e227f660708190b6581ecfe218a15c |
completed | April 17, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.