Triple
T18615544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Золотой Рог |
E455011
|
entity |
| Predicate | соединёнС |
P58112
|
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.
соединёнСМатериком
Indicates that something is physically connected to a mainland, rather than being isolated or separated (e.g., as an island).
-
B.
combinedIn
Indicates that two or more entities are merged, joined, or used together to form a single combined whole or context.
-
C.
partlyConnectedBy
Indicates that two entities are linked or joined by something in an incomplete, partial, or not fully continuous way.
-
D.
connectedByStraitTo
chosen
Indicates that one entity is geographically linked to another by a narrow body of water known as a strait.
-
E.
unites
Indicates that one entity brings together multiple entities into a single, cohesive whole or shared state.
- 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.