Triple
T17370455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Storelva |
E422295
|
entity |
| Predicate | hasNameInNorwegian |
P24009
|
FINISHED |
| Object | Storelva |
—
|
NE ONNED1 |
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: Storelva | Statement: [Storelva, hasNameInNorwegian, Storelva]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Storelva Context triple: [Storelva, hasNameInNorwegian, Storelva]
-
A.
Storelva
chosen
Storelva is a river in Ringerike, Norway, known locally as a small watercourse within the region’s inland river system.
-
B.
Lohavan
Lohavan is a sacred forest region within the Vraja Mandala pilgrimage area associated with the pastimes of Lord Krishna in Hindu tradition.
-
C.
Storvreten
Storvreten is a residential locality within Botkyrka Municipality in the Stockholm County area of Sweden.
-
D.
Stranorlar
Stranorlar is a small town in County Donegal, Ireland, situated on the River Finn and forming a twin town with nearby Ballybofey.
-
E.
Torvastad
Torvastad is a coastal village in Karmøy municipality in Rogaland county, southwestern Norway.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a68ff448190b505861e56df5b6d |
completed | April 19, 2026, 2:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a019568a27c8190af1bbe6db75f3e6f |
in_progress | May 11, 2026, 8:38 a.m. |
Created at: April 10, 2026, 5:44 a.m.