Triple
T23721520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Югорский Шар |
E586155
|
entity |
| Predicate | частьМорскогоПути |
P62174
|
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.
associatedWithSeaRoute
chosen
Indicates a relationship where something is connected or related to a particular sea route, such as by use, location, or relevance.
-
B.
hasSeaRouteConnection
Indicates that there exists a navigable maritime route linking two locations or entities.
-
C.
соединяетЧерезНеву
Indicates that one entity connects or links another entity by means of or across the Neva River.
-
D.
maritimeVariant
Indicates a version or form of something that is specifically adapted for or used in maritime (sea-related) contexts.
-
E.
partlyLocatedOn
Indicates that one entity is situated such that only a portion of it lies on or within the spatial extent of 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_69e24906fb108190a6898751e46bdc11 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b91177c08190bea6e62ed13e2495 |
completed | April 29, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:01 p.m.