Triple
T36345506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Дворцовая набережная |
E895052
|
entity |
| Predicate | пролегаетОт |
P151412
|
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 connects or links another entity by means of or across the Neva River.
-
B.
routeOf
Indicates that one entity is the path, course, or trajectory taken or followed by another entity (such as a vehicle, shipment, or signal).
-
C.
travelsThrough
Indicates that something moves along, passes across, or is routed via a particular path, medium, or location.
-
D.
routeAlong
chosen
Indicates that one entity follows, runs parallel to, or is situated along the course or path defined by another entity.
-
E.
parallelTransportCorridor
Indicates a relationship where one path, route, or connection is used to transport something in a way that preserves its structure or configuration relative to another, typically along a shared or corresponding trajectory.
- 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_69f7bb3ff1b08190802b1063d55d3923 |
completed | May 3, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a611a081908dd6aec1df3f4d7f |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:09 p.m.