Triple
T36345504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Дворцовая набережная |
E895052
|
entity |
| Predicate | расположенаВРайоне |
P83410
|
FINISHED |
| Object | Адмиралтейский район Санкт-Петербурга |
—
|
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: Адмиралтейский район Санкт-Петербурга | Statement: [Дворцовая набережная, расположенаВРайоне, Адмиралтейский район Санкт-Петербурга]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: расположенаВРайоне Context triple: [Дворцовая набережная, расположенаВРайоне, Адмиралтейский район Санкт-Петербурга]
-
A.
расположенаНа
Indicates that one entity is located on the surface or area of another entity.
-
B.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
C.
locatedInRegionalDistrict
chosen
Indicates that one entity is geographically situated within the boundaries of a specified regional district.
-
D.
находитсяК
Indicates that one entity is located at, in, or near another entity.
-
E.
locatedAlong
Indicates that one entity is situated adjacent to, or running beside, the length or course of another linear feature (such as a road, river, or railway).
- 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_69f76e4f437c8190a1af3ea2564f41f5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:09 p.m.