Triple
T2991655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lahn |
E80767
|
entity |
| Predicate | flowsThrough |
P225
|
FINISHED |
| Object | Marburg |
E174796
|
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: Marburg | Statement: [Lahn, flowsThrough, Marburg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Marburg Context triple: [Lahn, flowsThrough, Marburg]
-
A.
Marburg
chosen
Marburg is a historic university town in central Germany known for its well-preserved medieval old town and the Philipps-Universität, one of the oldest Protestant universities in the world.
-
B.
Vienenburg
Vienenburg is a district of Goslar in Lower Saxony, Germany, known for its historic town center and proximity to the Harz Mountains.
-
C.
Landsberg
Landsberg is a town in the Saalekreis district of the German state of Saxony-Anhalt.
-
D.
Neustadt
Neustadt is a district of the Austrian city of Salzburg, known for its central urban character within the historic and cultural landscape of the city.
-
E.
Neustadt
Neustadt is a vibrant district of Dresden, Germany, known for its historic architecture, lively arts scene, and numerous bars, cafes, and cultural venues.
- 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_69ad8b16c3488190b47b6aa7a59a335b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99df69d08190a0e25efb0dc8d653 |
completed | March 8, 2026, 3:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b109039cfc8190a286c83df752967e |
completed | March 11, 2026, 6:17 a.m. |
Created at: March 8, 2026, 2:59 p.m.