Triple
T17797923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Šibenik |
E444339
|
entity |
| Predicate | cathedralArchitecturalStyle |
P23266
|
FINISHED |
| Object | Gothic |
—
|
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: Gothic | Statement: [Šibenik, cathedralArchitecturalStyle, Gothic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cathedralArchitecturalStyle Context triple: [Šibenik, cathedralArchitecturalStyle, Gothic]
-
A.
hasCathedralStyle
chosen
Indicates that something possesses or is characterized by a particular architectural style associated with a cathedral.
-
B.
cathedralChurch
Indicates that one church serves as the cathedral (principal church and episcopal seat) of another ecclesiastical jurisdiction or entity.
-
C.
parishChurchArchitectureStyle
Indicates the architectural style or design tradition in which a parish church is built or characterized.
-
D.
cathedralFeature
Indicates that one entity is a distinctive architectural or structural feature of a cathedral.
-
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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e487fcfdc8819086f41152860dfe18 |
completed | April 19, 2026, 7:45 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:13 a.m.