Triple
T33972491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Zeno Altarpiece |
E871031
|
entity |
| Predicate | hasPredellaScene |
P203821
|
FINISHED |
| Object | Agony in the Garden |
E108189
|
NE 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: Agony in the Garden | Statement: [San Zeno Altarpiece, hasPredellaScene, Agony in the Garden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPredellaScene Context triple: [San Zeno Altarpiece, hasPredellaScene, Agony in the Garden]
-
A.
hasMainAltarpiece
Indicates that an entity (typically a religious building or space) possesses a specific artwork or structure serving as its principal altarpiece.
-
B.
hasAltarPieceFrom
Indicates that an altar piece originates from, or is sourced from, a particular place, creator, or context.
-
C.
hasAltarpieceSubject
Indicates that an altarpiece features or is dedicated to a particular subject or theme.
-
D.
hasNotableAltarpiece
Indicates that an entity (typically a religious building or site) possesses a particularly significant or distinguished altarpiece.
-
E.
hadAltarpieceBy
Indicates that an entity (typically a religious building or space) possessed or featured an altarpiece created by a specified artist or maker.
- F. None of above. chosen
Provenance (5 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_69f3499da0188190ab1a4ff06fb06a2a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0212b3462c8190ba3587852cb10655 |
completed | May 11, 2026, 5:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3689ee8f24819085bebf1c7f866eb0 |
completed | June 20, 2026, 12:39 p.m. |
| PD | Predicate disambiguation | batch_6a020f3138a48190ac630e810939e881 |
completed | May 11, 2026, 5:17 p.m. |
| PDg | Predicate description generation | batch_6a0212b0f9b081908917bec8e61c9d2e |
completed | May 11, 2026, 5:32 p.m. |
Created at: May 1, 2026, 1:50 a.m.