Triple
T7392536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rüsselsheim am Main |
E170536
|
entity |
| Predicate | locatedOn |
P40
|
FINISHED |
| Object | Main River |
E113003
|
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: Main River | Statement: [Rüsselsheim am Main, locatedOn, Main River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Main River Context triple: [Rüsselsheim am Main, locatedOn, Main River]
-
A.
River Main
chosen
The River Main is a major waterway in central Germany that flows through cities such as Frankfurt before joining the Rhine.
-
B.
Kako River
The Kako River is a river in Japan whose name was used for the Imperial Japanese Navy cruiser Kako.
-
C.
Sure river
The Sure river is a Swiss watercourse that drains Lake Sempach and flows through the canton of Lucerne before joining larger river systems.
-
D.
Emme River
The Emme River is a Swiss river flowing through the Emmental region and the Swiss Plateau, known for its picturesque valleys and historical flooding events.
-
E.
Current River
The Current River is a clear, spring-fed river in the Ozarks of southern Missouri and northern Arkansas, popular for canoeing, fishing, and scenic recreation.
- 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_69c68a5e2c9081909e713ce866e0060a |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f224790c819099ceb7c7ac8d00f6 |
completed | March 27, 2026, 9:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c81ecf65388190a149efc77aedcd91 |
completed | March 28, 2026, 6:32 p.m. |
Created at: March 27, 2026, 3:09 p.m.