Triple
T35742192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gesù Nuovo |
E1033065
|
entity |
| Predicate | hasMainAltarStyle |
P109055
|
FINISHED |
| Object | Baroque high altar |
—
|
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: Baroque high altar | Statement: [Gesù Nuovo, hasMainAltarStyle, Baroque high altar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainAltarStyle Context triple: [Gesù Nuovo, hasMainAltarStyle, Baroque high altar]
-
A.
hasMainAltarFor
Indicates that a specific altar serves as the primary or central altar designated for a particular entity, such as a church, chapel, or religious space.
-
B.
hasAltarType
chosen
Indicates that an entity is associated with or characterized by a specific type or category of altar.
-
C.
hasAltarpiecesInStyle
Indicates that an entity possesses or features altarpieces that are created or designed in a specified artistic style.
-
D.
hasAltar
Indicates that one entity possesses, contains, or includes an altar as part of its features or components.
-
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_69f76e119d508190a3873cb302063832 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a02f2d6f35481909829d4ec710dcb0f |
completed | May 12, 2026, 9:28 a.m. |
| PD | Predicate disambiguation | batch_6a02f15a2460819080cb4be5b50221d0 |
completed | May 12, 2026, 9:22 a.m. |
Created at: May 3, 2026, 4:06 p.m.