Triple
T38377868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Дворцовый мост |
E893673
|
entity |
| Predicate | расположенНижеПоТечениюОт |
P115583
|
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.
hasRiverBelow
Indicates that one entity is located above another such that a river lies physically below it.
-
B.
watercourseBelow
chosen
Indicates that one watercourse lies downstream or at a lower elevation relative to another watercourse.
-
C.
situatedUpstreamOf
Indicates that one entity is located in the direction from which a flow (such as water, traffic, or a process stream) originates relative to another entity along the same path or system.
-
D.
navigableInLowerCourse
Indicates that a watercourse is suitable for navigation specifically in its lower (downstream) section.
-
E.
hasLowerCourseNear
Indicates that the lower section of a course (such as a river or path) is located in close proximity to a specified reference entity or area.
- 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_69f76e4b1f748190a380696a16eae4a2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.