Triple
T11763391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Geller Altarpiece |
E279710
|
entity |
| Predicate | panelConfiguration |
P31593
|
FINISHED |
| Object | polyptych |
—
|
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: polyptych | Statement: [The Geller Altarpiece, panelConfiguration, polyptych]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: panelConfiguration Context triple: [The Geller Altarpiece, panelConfiguration, polyptych]
-
A.
panelArea
Indicates the total surface area covered or occupied by a specific panel.
-
B.
panelDivision
chosen
Indicates a relationship where a larger panel or board is divided into smaller sections or segments.
-
C.
displayConfiguration
Indicates a relationship where one entity defines or presents the arrangement, layout, or settings used to visually display another entity.
-
D.
controlLayout
Indicates that one entity determines or manages the spatial or structural arrangement of another entity.
-
E.
configuration
Indicates that one entity specifies or defines the arrangement, setup, or parameter settings under which another entity operates or is structured.
- 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_69d6ab01d2688190ad8ed6bda487eaa5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a5248e0881909ed1b4df7be422f7 |
completed | April 10, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69d88a829fe481909cc5431de7d6058e |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.