Triple
T26007413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaalimaa |
E646795
|
entity |
| Predicate | borderCrossingNameInFinnish |
P172760
|
FINISHED |
| Object | Vaalimaan rajanylityspaikka |
—
|
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: Vaalimaan rajanylityspaikka | Statement: [Vaalimaa, borderCrossingNameInFinnish, Vaalimaan rajanylityspaikka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderCrossingNameInFinnish Context triple: [Vaalimaa, borderCrossingNameInFinnish, Vaalimaan rajanylityspaikka]
-
A.
borderPostName
Indicates the specific name assigned to a border post where a boundary crossing or checkpoint is located.
-
B.
borderCrossingNameInArabic
Indicates the Arabic-language name assigned to a specific border crossing.
-
C.
hasBorderCrossingSide
Indicates that one side of a border crossing is associated with or located on a particular boundary or segment of that crossing.
-
D.
borderCrossingRouteTo
Indicates a route or path used to travel across a border from one place or jurisdiction to another.
-
E.
borderTownAcrossBorder
Indicates that a town lies on one side of a border directly opposite or adjacent to a town on the other side of that border.
- F. None of above. chosen
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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6b0d21dd08190a9883ff71c94c71c |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6afeaaef88190aefa97e83f8db906 |
completed | May 3, 2026, 2:16 a.m. |
Created at: April 22, 2026, 9:01 a.m.