Triple
T9641650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fürstenfeldbruck district |
E233084
|
entity |
| Predicate | traversedBy |
P225
|
FINISHED |
| Object | Amper River |
E816751
|
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: Amper River | Statement: [Fürstenfeldbruck district, traversedBy, Amper River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Amper River Context triple: [Fürstenfeldbruck district, traversedBy, Amper River]
-
A.
Amper River
chosen
The Amper River is a Bavarian river that flows through Upper Bavaria, including the district of Freising, before joining the Isar River.
-
B.
Aure River
The Aure River is a small waterway in Normandy, northwestern France, that flows through the historic town of Bayeux before joining the Vire River.
-
C.
Sée River
The Sée River is a coastal river in northwestern France that flows through Normandy before emptying into the Bay of Mont-Saint-Michel.
-
D.
Allier River
The Allier River is a major river in central France, known for its largely unspoiled natural course and as a tributary of the Loire.
-
E.
Avre River
The Avre River is a watercourse in northern France that flows through the Picardy region before joining the Somme River.
- 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_69ca848a5a908190aad251f4137b0c3a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b566a2881909ab3f9502b1c3c8d |
completed | April 1, 2026, 10:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2cb2aaef481908a7be61bbfc3b008 |
completed | April 5, 2026, 8:50 p.m. |
Created at: March 30, 2026, 8:12 p.m.