Triple
T26007389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaalimaa |
E646795
|
entity |
| Predicate | borderCrossingOnRoad |
P128541
|
FINISHED |
| Object | Helsinki–Saint Petersburg route |
—
|
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: Helsinki–Saint Petersburg route | Statement: [Vaalimaa, borderCrossingOnRoad, Helsinki–Saint Petersburg route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderCrossingOnRoad Context triple: [Vaalimaa, borderCrossingOnRoad, Helsinki–Saint Petersburg route]
-
A.
crossedByHighway
Indicates that a highway passes across or through the extent of a given entity or area.
-
B.
borderCrossingRouteTo
chosen
Indicates a route or path used to travel across a border from one place or jurisdiction to another.
-
C.
roadCrossingBetween
Indicates that a road crossing (such as a crosswalk or intersection crossing) exists between two locations or road segments, connecting them for passage across the road.
-
D.
borderPostLocatedOnHighway
Indicates that a border control post is situated along or directly on a specific highway.
-
E.
crossesCityLimit
Indicates that an entity moves from outside to inside, or inside to outside, the defined boundary of a city.
- 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_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 22, 2026, 9:01 a.m.