Triple
T17071875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaunas Cathedral Basilica |
E414241
|
entity |
| Predicate | cathedralSince |
P125745
|
FINISHED |
| Object | 1895 |
—
|
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: 1895 | Statement: [Kaunas Cathedral Basilica, cathedralSince, 1895]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cathedralSince Context triple: [Kaunas Cathedral Basilica, cathedralSince, 1895]
-
A.
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.
-
B.
cathedralChurch
Indicates that one church serves as the cathedral (principal church and episcopal seat) of another ecclesiastical jurisdiction or entity.
-
C.
coCathedral
Indicates that a church shares the status and functions of a cathedral with another cathedral within the same diocese or ecclesiastical jurisdiction.
-
D.
cathedralFeature
Indicates that one entity is a distinctive architectural or structural feature of a cathedral.
-
E.
usesCathedralFor
Indicates that an entity employs or makes use of a cathedral for a particular purpose or activity.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbc1b7d48190979a848b4188cb22 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
| PDg | Predicate description generation | batch_69e3753f93c88190808fec5692f66699 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:34 a.m.