Triple
T9745831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Main River region |
E236304
|
entity |
| Predicate | containsCity |
P294
|
FINISHED |
| Object | Bamberg |
E134924
|
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: Bamberg | Statement: [Main River region, containsCity, Bamberg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bamberg Context triple: [Main River region, containsCity, Bamberg]
-
A.
Bamberg
chosen
Bamberg is a historic city in northern Bavaria, Germany, renowned for its well-preserved medieval old town and status as a UNESCO World Heritage Site.
-
B.
Coburg
Coburg is a suburb in Melbourne, Australia, known for its diverse community, historic architecture, and access to the city via major tram routes.
-
C.
Coburg
Coburg is a historic town in northern Bavaria, Germany, known for its well-preserved medieval architecture and its former role as the seat of the Duchy of Saxe-Coburg and Gotha.
-
D.
Regensburg
Regensburg is a historic city in southeastern Germany known for its well-preserved medieval old town on the Danube River.
-
E.
Straubing
Straubing is a Bavarian town on the Danube River known for its historic city center and role as a regional economic and educational hub.
- 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_69ca84d3e24481908a476e2231123cf9 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9f65ad788190b68d731b6f516d93 |
completed | April 1, 2026, 10:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e5561714a081909cbf1cc7d5d0ac0a |
completed | April 19, 2026, 10:24 p.m. |
Created at: March 30, 2026, 8:23 p.m.