Triple
T4589844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golden Horn Bay |
E103455
|
entity |
| Predicate | isCoreWaterfrontOf |
P19053
|
FINISHED |
| Object | central Vladivostok |
—
|
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: central Vladivostok | Statement: [Golden Horn Bay, isCoreWaterfrontOf, central Vladivostok]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCoreWaterfrontOf Context triple: [Golden Horn Bay, isCoreWaterfrontOf, central Vladivostok]
-
A.
isWaterfrontBuilding
Indicates that a building is located directly adjacent to a body of water, such as a river, lake, or ocean.
-
B.
isWaterfrontThoroughfare
Indicates that a thoroughfare (such as a road, street, or path) is located directly along or adjacent to a body of water.
-
C.
hasWaterfrontArea
chosen
Indicates that an entity possesses or includes an area directly adjacent to or bordering a body of water.
-
D.
hasWaterfrontPark
Indicates that a place or area includes or is associated with a park located directly along a body of water.
-
E.
isInlandWaterwayCommunity
Indicates that a community is located along or associated with an inland waterway, such as a river, canal, or lake, rather than on open coastal waters.
- 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_69bd43dccaf08190aa89e9991a289719 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd592232888190af33c47636ca835d |
completed | March 20, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69bd522acbcc8190bf24d9517793a2c1 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:11 p.m.