Triple
T18615565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Золотой Рог |
E455011
|
entity |
| Predicate | являетсяМестом |
P7849
|
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.
portraysPlace
Indicates that one entity visually or narratively represents or depicts a particular place.
-
B.
isSiteOf
chosen
Indicates that a location or place serves as the setting or host for a particular event, activity, or feature.
-
C.
gatheringPlace
Indicates a location where entities come together or assemble, typically for a shared activity, purpose, or event.
-
D.
hasPlaceIn
Indicates that one entity occupies, is located within, or holds a specific position in another entity or context.
-
E.
targetedPlace
Indicates that an entity intentionally directed an action, operation, or influence toward a specific place or location.
- 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.