Triple
T31789210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Зелёный мост |
E811414
|
entity |
| Predicate | расположенВозле |
P61362
|
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.
oftenLocatedNear
Indicates that one entity is frequently found in close physical proximity to another entity.
-
B.
расположенаНа
Indicates that one entity is located on the surface or area of another entity.
-
C.
situatedNextTo
Indicates that one entity is located immediately beside another, with no significant separation between them.
-
D.
locatedInOrAdjacentTo
Indicates that one entity is either situated within the boundaries of another entity or directly next to it, sharing a common border or edge.
-
E.
nearbyTo
chosen
Indicates that one entity is located close in distance or position to 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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b21e7e088190832a3db585daea1c |
completed | May 3, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 30, 2026, 11:38 p.m.