Triple
T16060823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chapel of St Kinga |
E389604
|
entity |
| Predicate | hasSideChapel |
P34531
|
FINISHED |
| Object | side altars dedicated to saints |
—
|
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: side altars dedicated to saints | Statement: [Chapel of St Kinga, hasSideChapel, side altars dedicated to saints]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSideChapel Context triple: [Chapel of St Kinga, hasSideChapel, side altars dedicated to saints]
-
A.
hasChapels
chosen
Indicates that one entity contains, includes, or is associated with one or more chapels.
-
B.
hasNarthex
Indicates that one architectural structure (typically a church) includes or is equipped with a narthex area.
-
C.
hasTransept
Indicates that one architectural structure includes or features a transept as part of its design.
-
D.
housedInChapel
Indicates that something is located, kept, or contained within a chapel.
-
E.
hasSacristy
Indicates that a religious building includes or is associated with a sacristy (a room where sacred vessels, vestments, and liturgical items are kept and prepared).
- 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e18272f2288190a17d45fb01cc2b07 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:57 a.m.