Triple
T17804159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mariinsk Canal System |
E444509
|
entity |
| Predicate | connectedSea |
P49633
|
FINISHED |
| Object | Caspian Sea via Volga River |
—
|
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: Caspian Sea via Volga River | Statement: [Mariinsk Canal System, connectedSea, Caspian Sea via Volga River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedSea Context triple: [Mariinsk Canal System, connectedSea, Caspian Sea via Volga River]
-
A.
seaConnection
chosen
Indicates a relationship where two places are connected or accessible to each other via the sea, such as by maritime routes or coastal adjacency.
-
B.
touchesSea
Indicates that one entity is in direct physical contact with the sea or coastline of another entity.
-
C.
endSea
Indicates that something marks the boundary or termination point of a sea or sea area.
-
D.
seaOf
Indicates a relationship where one entity is metaphorically or literally surrounded or filled by another like a vast sea, emphasizing overwhelming abundance or expansiveness.
-
E.
adjacentSea
Indicates that one geographic entity directly borders or is next to a particular sea.
- 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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48802bcfc8190a138164d11081ab8 |
completed | April 19, 2026, 7:45 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:14 a.m.