Triple
T2426970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Traiectum |
E53551
|
entity |
| Predicate | locatedOn |
P40
|
FINISHED |
| Object | river Rhine |
E13461
|
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: river Rhine | Statement: [Traiectum, locatedOn, river Rhine]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: river Rhine Context triple: [Traiectum, locatedOn, river Rhine]
-
A.
Rhine
chosen
The Rhine is one of Europe's most important rivers, historically serving as a vital trade route and cultural boundary from the Alps through Germany to the North Sea.
-
B.
Rhens
Rhens is a historic town on the Rhine River in western Germany, known for its medieval role as a meeting place of the prince-electors of the Holy Roman Empire.
-
C.
High Rhine
The High Rhine is a stretch of the Rhine River in Central Europe, flowing swiftly between Lake Constance and Basel and forming part of the border between Germany and Switzerland.
-
D.
Rijn
Rijn is the Dutch name for the major European river known in English as the Rhine.
-
E.
Old Rhine
The Old Rhine is a historic branch of the Rhine River in the western Netherlands that flows through cities such as Leiden before reaching the North Sea.
- 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_69ab495c44d48190b7235b23719bc3f6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abc99b95548190b77d36de9adfe3bb |
completed | March 7, 2026, 6:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b2e803e994819085dae09224fae2a3 |
completed | March 12, 2026, 4:21 p.m. |
Created at: March 6, 2026, 9:42 p.m.