Triple
T12337769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarrebourg |
E294134
|
entity |
| Predicate | crossedBy |
P416
|
FINISHED |
| Object | river Sarre |
E994190
|
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 Sarre | Statement: [Sarrebourg, crossedBy, river Sarre]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: river Sarre Context triple: [Sarrebourg, crossedBy, river Sarre]
-
A.
river Sarre
chosen
The river Sarre is a waterway in northeastern France and western Germany that flows through the Lorraine region before joining the Moselle River.
-
B.
Moselle River
The Moselle River is a major European waterway flowing through France, Luxembourg, and Germany, renowned for its scenic valleys and wine-producing regions.
-
C.
Meurthe River
The Meurthe River is a river in northeastern France that flows through the city of Nancy before joining the Moselle.
-
D.
Sambre
The Sambre is a major river in northern France and southern Belgium that flows through the Walloon region before joining the Meuse at Namur.
-
E.
Moselle
Moselle is a department in northeastern France, bordering Germany and Luxembourg, known for its strategic location, industrial history, and mixed French-German cultural heritage.
- 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_69d6ab6ae0dc8190b1522a9c1c55c114 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f678698819091462b44ff3435f6 |
completed | April 10, 2026, 6:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f671837a5c81908a7f41ac7e2bef59 |
completed | May 2, 2026, 9:49 p.m. |
Created at: April 8, 2026, 9:53 p.m.