Triple
T30419800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Иоанновский равелин |
E773866
|
entity |
| Predicate | расположенНаБерегу |
P105947
|
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.
locatedOnCoastAt
Indicates that one entity is situated on the coastline at the specific location represented by another entity.
-
B.
basedOnCoast
Indicates that something is situated along, adjacent to, or directly influenced by a coastline.
-
C.
touchesSea
Indicates that one entity is in direct physical contact with the sea or coastline of another entity.
-
D.
locatedOnEasternShoreOf
Indicates that one entity is situated on the eastern shore or bank of another geographic feature, such as a body of water or landform.
-
E.
расположенаНа
chosen
Indicates that one entity is located on the surface or area of 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_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.