Triple
T35971108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Изборская крепость |
E1040285
|
entity |
| Predicate | ближайшаяГраница |
P46305
|
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.
borderingCountryNearby
Indicates that one country is geographically close to, but does not necessarily share a direct land border with, another country.
-
B.
countryBorderProximity
Indicates that one country is geographically close to or directly bordering another country.
-
C.
distanceToBorder
Indicates the measured or estimated spatial separation between a given entity or location and the nearest relevant border or boundary.
-
D.
distanceToRussianBorder_km
Indicates the physical distance, measured in kilometers, between a given location and the nearest point on the Russian border.
-
E.
nearInternationalBoundary
chosen
Indicates that one entity is located close to an international boundary separating two or more countries.
- 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_69f76e27758c81909b711cf38a130aaf |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7acaec1508190a38f2ac9cc5383e7 |
completed | May 3, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.