Triple
T522621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kazan Cathedral |
E10850
|
entity |
| Predicate | hasDomeType |
P13536
|
FINISHED |
| Object | single large central dome |
—
|
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: single large central dome | Statement: [Kazan Cathedral, hasDomeType, single large central dome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDomeType Context triple: [Kazan Cathedral, hasDomeType, single large central dome]
-
A.
hasMainDome
chosen
Indicates that an entity possesses a primary or central dome as a defining architectural feature.
-
B.
hasHullType
Indicates that an entity possesses or is characterized by a specific type or form of hull.
-
C.
heightOfDome
Indicates the measured vertical extent or elevation of a dome structure from its base to its highest point.
-
D.
domeCompleted
Indicates that the construction or formation of a dome structure has been fully finished.
-
E.
hasConeType
Indicates that an entity possesses or is associated with a specific type or category of cone.
- 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1b372408190b3918fec45444674 |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f018129c81909494450fcba71b59 |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.