Triple
T30419830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | правый берег Невы |
E773867
|
entity |
| Predicate | пересекаетсяМостамиС |
P106621
|
FINISHED |
| Object | левый берег Невы |
—
|
LITERAL FINISHED |
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.
hasBridgeCrossings
chosen
Indicates that one entity has one or more bridge structures that span across or connect over another entity (such as a road, river, or area).
-
B.
riverCrossedByMaintainedBridges
Indicates that a river is spanned by one or more bridges that are actively maintained in usable condition.
-
C.
bridgesBetween
Indicates a relationship where something connects or links two otherwise separate entities, contexts, or states, enabling interaction or transition between them.
-
D.
hasNumberOfBridges
Indicates the quantitative relationship specifying how many bridges are associated with a given entity.
-
E.
hasBridgeOrFerryConnection
Indicates that there exists a bridge or ferry link enabling direct passage or transport between the related entities.
- 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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6864cd7548190b3e12ef2fe253ad8 |
completed | May 2, 2026, 11:18 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:05 p.m.