Triple
T5634784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fyris River |
E147920
|
entity |
| Predicate | nameInSwedish |
P11737
|
FINISHED |
| Object | Fyrisån |
E147920
|
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: Fyrisån | Statement: [Fyris River, nameInSwedish, Fyrisån]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fyrisån Context triple: [Fyris River, nameInSwedish, 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.
Eidselva
Eidselva is a river in Norway that serves as one of the main waterways feeding into the lake Norsjø.
-
C.
Ångerman River
The Ångerman River is a major river in northern Sweden known for its long course through forested landscapes before emptying into the Gulf of Bothnia.
-
D.
Dalälven
Dalälven is a major river in central Sweden known for its extensive watershed, hydroelectric power stations, and rich natural and recreational areas.
-
E.
Moldeelva
Moldeelva is a river flowing through the Norwegian town of Molde, contributing to its landscape and local environment.
- 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_69c00907bc8881909ed760d3ed73ef35 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0226118548190877793dadf6cacba |
completed | March 22, 2026, 5:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c097d0234881908f6716979a2ade3a |
completed | March 23, 2026, 1:30 a.m. |
Created at: March 22, 2026, 3:41 p.m.