Triple
T23851736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Соборная площадь |
E592186
|
entity |
| Predicate | архитектурнаяДоминианта |
P154184
|
FINISHED |
| Object | главный собор города |
—
|
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: главный собор города | Statement: [Соборная площадь, архитектурнаяДоминианта, главный собор города]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: архитектурнаяДоминианта Context triple: [Соборная площадь, архитектурнаяДоминианта, главный собор города]
-
A.
domeInspiredBy
Indicates that the design or structure of a dome is influenced or derived from another dome or architectural source.
-
B.
eraOfManyBuildings
Indicates a time period during which many buildings were constructed or existed.
-
C.
pantheon
Indicates a relationship where a group of deities collectively belong to or are recognized within the same religious or mythological system.
-
D.
architecturalComplex
Indicates a relationship where multiple architectural structures or elements are grouped and function together as a single, integrated complex.
-
E.
allyOfRome
Indicates a relationship where one entity is politically or militarily aligned with, and offers support or cooperation to, Rome.
- 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_69e25d221d908190b9b502ad31e66a3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c987c3208190bf3f210d12106927 |
completed | April 29, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 8:11 p.m.