Triple
T26315189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columba Altarpiece |
E661951
|
entity |
| Predicate | rightPanel |
P73313
|
FINISHED |
| Object | Presentation of Christ in the Temple |
—
|
NE NERFINISHED |
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: Presentation of Christ in the Temple | Statement: [Columba Altarpiece, rightPanel, Presentation of Christ in the Temple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rightPanel Context triple: [Columba Altarpiece, rightPanel, Presentation of Christ in the Temple]
-
A.
leftPanelSubject
Indicates that an entity serves as the primary subject or focus displayed in the left panel of a user interface or layout.
-
B.
proposedRight
Indicates that one party has put forward or suggested granting a specific right to another party or entity.
-
C.
rightHalfFeatures
chosen
Indicates that the associated features pertain specifically to the right half of an object, image, or spatial region.
-
D.
navigationRightType
Indicates the type or category of a right or permission related to navigation or movement in a given context.
-
E.
selectionRight
Indicates that one entity is chosen or designated as the correct or preferred option among a set of possible selections.
- 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_69ee812e73048190aae587f1d51e5a06 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f612607c388190ab61d1ac7d18e08d |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
Created at: April 26, 2026, 10:24 p.m.