Triple
T7474607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Constance |
E176598
|
entity |
| Predicate | inflow |
P415
|
FINISHED |
| Object | Bregenzer Ach |
E493376
|
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: Bregenzer Ach | Statement: [Lake Constance, inflow, Bregenzer Ach]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bregenzer Ach Context triple: [Lake Constance, inflow, Bregenzer Ach]
-
A.
Bregenzer Ach
chosen
Bregenzer Ach is a river in western Austria that flows through the state of Vorarlberg before joining the Rhine.
-
B.
Eisacktal
Eisacktal is a scenic valley in South Tyrol, northern Italy, known for its alpine landscapes, vineyards, and historic towns along the Eisack River.
-
C.
Gasteiner Ache
Gasteiner Ache is a mountain river in the Austrian Alps that flows through the Gastein Valley before joining the Salzach River.
-
D.
Ötztaler Ache
Ötztaler Ache is a fast-flowing alpine river in Tyrol, Austria, known for draining the Ötztal valley and offering popular whitewater rafting and kayaking routes.
-
E.
Kitzbüheler Ache
Kitzbüheler Ache is a river in the Tyrol region of Austria that flows through the town of Kitzbühel and its surrounding alpine landscape.
- 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_69c69f236ce08190a04d7679f03b29b2 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f417fbb48190b134eaf1da1b4289 |
completed | March 27, 2026, 9:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c83c655fcc8190a23d8dd69a70431c |
completed | March 28, 2026, 8:39 p.m. |
Created at: March 27, 2026, 3:41 p.m.