Triple
T1682085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uppsala |
E36359
|
entity |
| Predicate | river |
P165
|
FINISHED |
| Object | Fyris River |
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 River | Statement: [Uppsala, river, Fyris River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fyris River Context triple: [Uppsala, river, Fyris River]
-
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.
Arve River
The Arve River is a glacial river in the Alps that flows through France and Switzerland, notably passing through Geneva before joining the Rhône.
-
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.
Vesle River
The Vesle River is a waterway in northeastern France that flows through the city of Reims and is a tributary of the Aisne River.
-
E.
Min River
The Min River is a significant river in southwestern China that flows through Sichuan Province and plays a key role in the region’s ecology, agriculture, and water resources.
- 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_69a886139ed081909af0940aa9313512 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa627935888190ad793a720bb6cba5 |
completed | March 6, 2026, 5:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad71bf1998819094d3eb67c6e6bafd |
completed | March 8, 2026, 12:55 p.m. |
Created at: March 4, 2026, 7:29 p.m.