Triple
T15760517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Børselv |
E382082
|
entity |
| Predicate | hasNearbyRiver |
P8567
|
FINISHED |
| Object | Børselva |
E389229
|
NE FINISHED |
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: Børselva | Statement: [Børselv, hasNearbyRiver, Børselva]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Børselva Context triple: [Børselv, hasNearbyRiver, Børselva]
-
A.
Børselva
chosen
Børselva is a river in northern Norway known for flowing into Porsangerfjorden and for its scenic Arctic landscape and salmon fishing.
-
B.
Fykseelva
Fykseelva is a river flowing through the municipality of Kvam in Vestland county, western Norway, known for its scenic valley and salmon fishing.
-
C.
Verdalselva
Verdalselva is a river in Trøndelag county, Norway, known for flowing through the Verdalen valley and supporting local agriculture, recreation, and salmon fishing.
-
D.
Krokstadelva
Krokstadelva is a town in Viken county, Norway, situated along the Drammenselva river and known historically for its industrial and residential character.
-
E.
Solbergelva
Solbergelva is a village in Viken county, Norway, situated along the Drammenselva river and functioning largely as a residential suburb of Drammen.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e050b52c548190a0ffa4493a4eb15c |
completed | April 16, 2026, 3 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffa9361f5c8190b68702154d05bbc2 |
completed | May 9, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:47 a.m.