Triple
T9161608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moltkebrücke |
E219836
|
entity |
| Predicate | hasView |
P854
|
FINISHED |
| Object | Spreebogen |
E779624
|
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: Spreebogen | Statement: [Moltkebrücke, hasView, Spreebogen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Spreebogen Context triple: [Moltkebrücke, hasView, Spreebogen]
-
A.
Spreebogen
chosen
Spreebogen is a prominent riverside area in central Berlin known for its sweeping bend of the River Spree and its concentration of major government and cultural buildings.
-
B.
Schwibbogen
A Schwibbogen is a traditional German decorative candle arch, typically made of wood and displayed in windows during the Christmas season, especially in the Ore Mountains region.
-
C.
Schwerteck
Schwerteck is a mountain peak in the Glockner Group of the Austrian Alps.
-
D.
Kleeberg
Kleeberg is a Polish surname most notably associated with General Franciszek Kleeberg, a commander in the early stages of World War II.
-
E.
Bösperde
Bösperde is a district of the town of Menden in North Rhine-Westphalia, Germany, known as a primarily residential suburban area.
- 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_69ca83e3633c81908688a9fa2306ba99 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccaa2ac0508190b2f5c801c2c26d66 |
completed | April 1, 2026, 5:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d054770a0c819095cf0a7cc8d1a057 |
completed | April 3, 2026, 11:59 p.m. |
Created at: March 30, 2026, 7:21 p.m.