Triple
T32515677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Сенатская площадь |
E831053
|
entity |
| Predicate | имеетПанорамуНа |
P29603
|
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.
hasPanoramicView
chosen
Indicates that something offers a wide, unobstructed view over a broad surrounding area.
-
B.
panoramaDesigner
Indicates a relationship where an entity is responsible for designing or creating panoramic views or panorama-related content for another entity or context.
-
C.
panoramaCreatedFor
Indicates that a panorama (a wide-angle composite image or view) has been generated or produced specifically for a particular entity or context.
-
D.
hasSummitPanorama
Indicates that a summit location offers a panoramic view or image captured from its highest point.
-
E.
hasScenicViewOf
Indicates that one entity offers a visually appealing or picturesque view of another entity.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1 a.m.