Triple
T23851723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Соборная площадь |
E592186
|
entity |
| Predicate | расположениеОтносительноСобора |
P154183
|
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.
positionInChurch
Indicates that one entity holds a specific role, office, or rank within a church organization or hierarchy.
-
B.
placeOfConsecration
Indicates the specific place where a religious or ceremonial consecration of something or someone took place.
-
C.
locatedInTheChurch
Indicates that one entity is physically situated within or inside the church.
-
D.
ecclesiasticalCenter
Indicates that a place functions as a primary religious or church administrative hub for a surrounding area or community.
-
E.
floorLocationOfChurch
Indicates the specific floor or level within a building where the church is located.
- 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.