Triple
T36345537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Дворцовая набережная |
E895052
|
entity |
| Predicate | расположенаНапротив |
P3232
|
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.
positionedAgainst
Indicates that one entity is placed so that it directly faces or is set opposite to another entity, often in close or contacting alignment.
-
B.
расположенаНа
Indicates that one entity is located on the surface or area of another entity.
-
C.
opposingLocation
chosen
Indicates that two entities are located directly opposite each other, typically across a defined reference such as a street, corridor, or boundary.
-
D.
расположениеОтносительноСобора
Indicates the spatial positioning or orientation of something in relation to the cathedral.
-
E.
positionOpposed
Indicates that two entities hold positions or stances that are in direct conflict or opposition to each other.
- 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_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:09 p.m.