Triple
T10932632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Адмиралтейская набережная |
E258245
|
entity |
| Predicate | hasEmbankmentType |
P27578
|
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: [Адмиралтейская набережная, hasEmbankmentType, каменная набережная]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEmbankmentType Context triple: [Адмиралтейская набережная, hasEmbankmentType, каменная набережная]
-
A.
hasEmbankment
chosen
Indicates that one entity possesses or is characterized by an embankment, such as a raised structure built to contain, support, or protect against water or terrain.
-
B.
hasFloodplainType
Indicates that an area or location is associated with a specific type or classification of floodplain.
-
C.
hasFloodplain
Indicates that an area or location lies within the floodplain associated with a particular water body or flooding source.
-
D.
hasEstuaryType
Indicates the specific type or classification of an estuary associated with a given water body or location.
-
E.
hasFloodplains
Indicates that an area or region includes land that is subject to flooding, typically adjacent to a river or water body.
- 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_69d6aa8769b4819082bfe5e61b9017f0 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770a16cbc8190acd619defed7114c |
completed | April 9, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69d72e799f808190b6ab64fc7586a303 |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:23 p.m.