Triple
T29712058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Municipality of Vehkalahti |
E751807
|
entity |
| Predicate | wasBordering |
P162434
|
FINISHED |
| Object | Gulf of Finland |
—
|
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: Gulf of Finland | Statement: [Municipality of Vehkalahti, wasBordering, Gulf of Finland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasBordering Context triple: [Municipality of Vehkalahti, wasBordering, Gulf of Finland]
-
A.
hadBorder
chosen
Indicates that one entity shared a common boundary or frontier with another entity during a specified time period.
-
B.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
C.
wasFrontierBetween
Indicates that one entity historically served as the boundary or border region separating two other entities.
-
D.
hasBorderConflictWith
Indicates a relationship where two entities share a disputed boundary or are involved in an ongoing or historical conflict over their common border.
-
E.
borderWithin
Indicates that one region’s border lies entirely inside the boundary of another region.
- 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_69f0d62748848190b030d0a703629a7d |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672da10e08190907fec9b1a232f63 |
completed | May 2, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:31 p.m.