Triple
T18615553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Золотой Рог |
E455011
|
entity |
| Predicate | окружён |
P7850
|
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.
surrounds
chosen
Indicates that one entity is located all around another entity, enclosing or encircling it on multiple sides or completely.
-
B.
surroundedOnThreeSidesBy
Indicates that one entity is positioned so that three of its sides are directly bordered or enclosed by another entity.
-
C.
surroundedCity
Indicates that one city is encircled or completely enclosed by another city or its surrounding territory.
-
D.
around
Indicates that one entity is located or moves on all or most sides of another entity, encircling or surrounding it spatially.
-
E.
circumscribedBy
Indicates that one entity is completely enclosed or bounded on all sides by 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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54d04bdc48190b0213132923a7580 |
completed | April 19, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:45 a.m.