Triple
T32515668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Сенатская площадь |
E831053
|
entity |
| Predicate | ограниченаЗданием |
P174536
|
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.
buildingIncorporatedInto
Indicates that one building has been structurally or functionally integrated into another building as part of a combined or expanded construction.
-
B.
housedWithinComplex
Indicates that one entity is located inside and functionally part of a larger building or facility complex.
-
C.
occursInBuilding
Indicates that an event or activity takes place within a specific building.
-
D.
isLocatedInBuilding
Indicates that one entity is physically situated within or inside the structure of a particular building.
-
E.
locatedInBuildingWithFeature
Indicates that something is located in a building that possesses a specified feature or characteristic.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c4a2e4cc81909158364159fac689 |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 1 a.m.