Triple
T31890759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transcaucasian Socialist Federative Soviet Republic |
E814138
|
entity |
| Predicate | borderedSea |
P44290
|
FINISHED |
| Object | Black Sea |
E7745
|
NE 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: Black Sea | Statement: [Transcaucasian Socialist Federative Soviet Republic, borderedSea, Black Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderedSea Context triple: [Transcaucasian Socialist Federative Soviet Republic, borderedSea, Black Sea]
-
A.
borderingSeaAreaOf
Indicates that one entity is a sea area that directly borders or adjoins the coastline or maritime boundary of another entity.
-
B.
hasLandBorderWithSea
Indicates that an entity’s land area directly borders or touches a sea along its coastline.
-
C.
adjacentSea
chosen
Indicates that one geographic entity directly borders or is next to a particular sea.
-
D.
touchesSea
Indicates that one entity is in direct physical contact with the sea or coastline of another entity.
-
E.
nearestSea
Indicates that one location is the closest sea to a given place compared to all other seas.
- F. None of above.
Provenance (4 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_69f348ef817481908440e2250319bcc8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fed83b1d188190a318b0ad3003200a |
completed | May 9, 2026, 6:46 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2e7fc73a708190a1aaa76033b7a9f9 |
completed | June 14, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69fed78e03548190b6e6ad93ae8d131d |
completed | May 9, 2026, 6:43 a.m. |
Created at: April 30, 2026, 11:58 p.m.