Triple
T22095888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flustret bridge |
E546030
|
entity |
| Predicate | crosses |
P416
|
FINISHED |
| Object | Fyrisån |
—
|
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: Fyrisån | Statement: [Flustret bridge, crosses, Fyrisån]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fyrisån Context triple: [Flustret bridge, crosses, Fyrisån]
-
A.
Fyris River
chosen
The Fyris River is a notable waterway in eastern Sweden that flows through the city of Uppsala and is closely associated with its history and landscape.
-
B.
Lærdalselvi
Lærdalselvi is a renowned salmon river in western Norway, flowing through the Lærdal valley to the Sognefjord and known for both its fishing and scenic landscape.
-
C.
Klarälven
Klarälven is a major river in Norway and Sweden that flows south through Värmland before emptying into Lake Vänern.
-
D.
Stjørdalselva
Stjørdalselva is a river in Trøndelag county, Norway, known for flowing through the Stjørdal valley and being a popular destination for salmon fishing.
-
E.
Eidselva
Eidselva is a river in Norway that serves as one of the main waterways feeding into the lake Norsjø.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e36d03c8190a83a1ba802b7231b |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128e8f1f48190a5f1d9e96a6de688 |
completed | April 28, 2026, 9:38 p.m. |
Created at: April 16, 2026, 8:29 p.m.