Triple
T35679055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dolianova |
E1030950
|
entity |
| Predicate | architecturalStyleOfMainCathedral |
P607
|
FINISHED |
| Object | Romanesque |
—
|
NE NERFINISHED |
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: Romanesque | Statement: [Dolianova, architecturalStyleOfMainCathedral, Romanesque]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: architecturalStyleOfMainCathedral Context triple: [Dolianova, architecturalStyleOfMainCathedral, Romanesque]
-
A.
hasCathedralStyle
Indicates that something possesses or is characterized by a particular architectural style associated with a cathedral.
-
B.
hasMainCathedral
Indicates that an entity possesses or is associated with a primary cathedral that serves as its main ecclesiastical center.
-
C.
architecturalStyle
chosen
Indicates the architectural design tradition, movement, or style that characterizes the form and appearance of a structure or built work.
-
D.
parishChurchArchitectureStyle
Indicates the architectural style or design tradition in which a parish church is built or characterized.
-
E.
hasCathedralType
Indicates that an entity is associated with, classified by, or designated as having a specific type or category of cathedral.
- 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_69f76e0bb6608190ad3a1880be54a17d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:05 p.m.