Triple
T6320963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kholmsk |
E141734
|
entity |
| Predicate | isPortIn |
P65472
|
FINISHED |
| Object | Sea of Japan basin |
—
|
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: Sea of Japan basin | Statement: [Kholmsk, isPortIn, Sea of Japan basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPortIn Context triple: [Kholmsk, isPortIn, Sea of Japan basin]
-
A.
isInPort
Indicates that an entity (such as a vessel or vehicle) is currently located within or docked at a specific port.
-
B.
hasPortOn
Indicates that one entity possesses or is located adjacent to a port situated on another specified geographic or infrastructural feature (such as a coast, river, or lake).
-
C.
isPortCommunity
Indicates that an entity functions as or belongs to a community associated with a port, typically involving shared interests, activities, or governance related to port operations.
-
D.
isInlandPort
Indicates that a port facility is located inland, away from the open sea, typically on a river, canal, or lake, while still serving maritime or shipping functions.
-
E.
includesPort
chosen
Indicates that one entity contains, encompasses, or has as part of it a specific port or set of ports.
- 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_69c008d13b8c8190be47d896eb735605 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064c61f008190b316b9ff1023b057 |
completed | March 22, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69c060e5efc48190861b8266e5b0cc0c |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:29 p.m.