Triple
T28842890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cannons |
E728368
|
entity |
| Predicate | parishChurchInterior |
P38425
|
FINISHED |
| Object | rich Baroque decoration |
—
|
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: rich Baroque decoration | Statement: [Cannons, parishChurchInterior, rich Baroque decoration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parishChurchInterior Context triple: [Cannons, parishChurchInterior, rich Baroque decoration]
-
A.
parishChurchFeatures
chosen
Indicates that a parish church possesses or includes specific architectural, artistic, or functional features.
-
B.
parishChurchFeaturesWorkBy
Indicates that a parish church includes, displays, or incorporates a work created by a specified artist or maker.
-
C.
cathedralChurch
Indicates that one church serves as the cathedral (principal church and episcopal seat) of another ecclesiastical jurisdiction or entity.
-
D.
housedInChapel
Indicates that something is located, kept, or contained within a chapel.
-
E.
cathedral
Indicates that an entity is a cathedral, i.e., it has the status or function of a principal church, typically one that is the seat of a bishop.
- 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_69f0319e8e7c8190b37288c8845b9dbc |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 6:41 a.m.