Triple
T3002754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rijn |
E81826
|
entity |
| Predicate | GermanName |
P6492
|
FINISHED |
| Object | Rhein |
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: Rhein | Statement: [Rijn, GermanName, Rhein]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rhein Context triple: [Rijn, GermanName, Rhein]
-
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.
Rheine
Rheine is a German city in the state of North Rhine-Westphalia, known for its historical town center and location along the River Ems.
-
D.
Meuse
The Meuse is a major European river flowing through France, Belgium, and the Netherlands, historically important for transport, trade, and the development of surrounding regions.
-
E.
Meuse
Meuse is a department in northeastern France known for its rural landscapes and significant World War I battlefields, including Verdun.
- 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_69ad8b1c4de88190a83b7cefaa1f2842 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a1371c481909e214234afed1a65 |
completed | March 8, 2026, 3:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5627344648190b2794d4e71524bf4 |
completed | March 14, 2026, 1:28 p.m. |
Created at: March 8, 2026, 2:59 p.m.