Triple
T33713752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treriksröset |
E863814
|
entity |
| Predicate | isTripointOf |
P13730
|
FINISHED |
| Object | Norway–Sweden border |
—
|
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: Norway–Sweden border | Statement: [Treriksröset, isTripointOf, Norway–Sweden border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTripointOf Context triple: [Treriksröset, isTripointOf, Norway–Sweden border]
-
A.
hasTripoint
chosen
Indicates that three distinct regions, areas, or entities meet or share a common boundary point.
-
B.
isReferencePointFor
Indicates that one entity serves as a positional or conceptual basis used to locate, measure, or interpret another entity.
-
C.
isStartingPointOf
Indicates that something serves as the initial point or origin from which another thing, process, or path begins.
-
D.
isTransitPointOn
Indicates that one location serves as an intermediate transit point along a specified route, path, or journey.
-
E.
hasConfluencePointAt
Indicates that two or more flows, paths, or entities meet and merge at a specific point.
- 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_69f34989871c81908682e22a2fe4b829 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fabe07848190bd4f14ac6dfa35b6 |
completed | May 3, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:44 a.m.