Triple
T26007412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaalimaa |
E646795
|
entity |
| Predicate | connectedCountryOnOtherSide |
P86312
|
FINISHED |
| Object | Russia |
—
|
NE NERFINISHED |
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: Russia | Statement: [Vaalimaa, connectedCountryOnOtherSide, Russia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedCountryOnOtherSide Context triple: [Vaalimaa, connectedCountryOnOtherSide, Russia]
-
A.
borderingCountryOnOtherSide
Indicates that one country lies on the opposite side of a shared border relative to another country.
-
B.
connectsToCountryBorder
Indicates that one entity is directly adjacent to and touches the border of a specified country.
-
C.
relatedCountry
Indicates that there is a relevant or associated relationship between an entity and a specified country, without specifying the exact nature of that relationship.
-
D.
countryOnOtherSide
chosen
Indicates that one location is situated across a boundary or dividing feature (such as a border, river, or sea) from another country, on the opposite side.
-
E.
betweenCountry
Indicates a relationship or interaction that involves or occurs among 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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 22, 2026, 9:01 a.m.