Triple
T33604026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rygge Church |
E860797
|
entity |
| Predicate | hasAltarPieceFrom |
P193673
|
FINISHED |
| Object | 17th century |
—
|
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: 17th century | Statement: [Rygge Church, hasAltarPieceFrom, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAltarPieceFrom Context triple: [Rygge Church, hasAltarPieceFrom, 17th century]
-
A.
hadAltarpieceBy
Indicates that an entity (typically a religious building or space) possessed or featured an altarpiece created by a specified artist or maker.
-
B.
hasAltarpieceSubject
Indicates that an altarpiece features or is dedicated to a particular subject or theme.
-
C.
hasNotableAltarpiece
Indicates that an entity (typically a religious building or site) possesses a particularly significant or distinguished altarpiece.
-
D.
hasMainAltarpiece
Indicates that an entity (typically a religious building or space) possesses a specific artwork or structure serving as its principal altarpiece.
-
E.
hasAltarpieceHeight
Indicates the relationship specifying the height measurement of an altarpiece.
- F. None of above. chosen
Provenance (4 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_69f3497f35908190a2e9bbb9b96c7a3f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
| PDg | Predicate description generation | batch_69fd4f38728c8190b3271abc80882cfb |
completed | May 8, 2026, 2:49 a.m. |
Created at: May 1, 2026, 1:41 a.m.