Triple
T25169886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lomonosovskaya station |
E630290
|
entity |
| Predicate | servesRiverBank |
P39043
|
FINISHED |
| Object | Neva River bank in southeastern Saint Petersburg |
—
|
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: Neva River bank in southeastern Saint Petersburg | Statement: [Lomonosovskaya station, servesRiverBank, Neva River bank in southeastern Saint Petersburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesRiverBank Context triple: [Lomonosovskaya station, servesRiverBank, Neva River bank in southeastern Saint Petersburg]
-
A.
primaryRiverBank
Indicates that a river segment is primarily associated with or bordered by a particular river bank (e.g., left or right bank) as its main adjoining side.
-
B.
locatedOnBankOfRiver
chosen
Indicates that one entity is situated along or directly adjacent to the bank of a specified river.
-
C.
riverBankOnSouthSide
Indicates that a river bank is located on the southern side of a specified river or watercourse.
-
D.
riverBankOnEastSide
Indicates that a river bank is located on the eastern side of a river or watercourse.
-
E.
operatesOnRiver
Indicates that an entity conducts its operations or activities on, along, or directly involving a river.
- 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_69e75a87c9b88190ab60731902a99750 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 21, 2026, 12:19 p.m.