Triple
T32729353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finland |
E836905
|
entity |
| Predicate | hasMaritimeBorder |
P39564
|
FINISHED |
| Object | Sweden |
—
|
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: Sweden | Statement: [Finland, hasMaritimeBorder, Sweden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaritimeBorder Context triple: [Finland, hasMaritimeBorder, Sweden]
-
A.
hasLandBorderWithSea
Indicates that an entity’s land area directly borders or touches a sea along its coastline.
-
B.
bordersStateAcrossSea
Indicates that one state is separated from another by a sea but still directly borders it across that body of water.
-
C.
borderingCountryAcrossWater
Indicates that one country is geographically separated from another by a body of water yet lies close enough to be considered a neighboring country across that water.
-
D.
sharesMaritimeBorders
chosen
Indicates that two entities have adjacent territorial waters or maritime zones that touch or overlap, forming a shared sea boundary.
-
E.
hasMaritimeConnection
Indicates a relationship in which an entity is linked to seas, oceans, or maritime activities, such as shipping, navigation, or coastal operations.
- 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_69f34935fb048190ad4967420581f835 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a00a846a8f881908b073ad13a5af6ca |
completed | May 10, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_6a00a7aae194819085e1a2fd406f7922 |
completed | May 10, 2026, 3:43 p.m. |
Created at: May 1, 2026, 1:11 a.m.