Triple
T6358405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlin public transport network |
E143047
|
entity |
| Predicate | connectsTo |
P845
|
FINISHED |
| Object | Bernau bei Berlin |
E311039
|
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: Bernau bei Berlin | Statement: [Berlin public transport network, connectsTo, Bernau bei Berlin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bernau bei Berlin Context triple: [Berlin public transport network, connectsTo, Bernau bei Berlin]
-
A.
Bernau bei Berlin
chosen
Bernau bei Berlin is a historic town in the German state of Brandenburg, located just northeast of Berlin and known for its well-preserved medieval city walls.
-
B.
Degendorf
Degendorf is a locality within the Bavarian town and district of Lichtenfels in Germany.
-
C.
Mahlsdorf
Mahlsdorf is a locality in the borough of Marzahn-Hellersdorf in eastern Berlin, Germany, known for its residential character and historic village center.
-
D.
Schönewalde
Schönewalde is a town in the state of Brandenburg, Germany, known for hosting a German Air Force base.
-
E.
Beuthen
Beuthen is the historical German name for the city of Bytom in southern Poland’s Upper Silesia region.
- 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_69c008d7a9c4819098d647ec47776917 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c067f5bdd481909cf9db595ddb27df |
completed | March 22, 2026, 10:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c62d5f134c8190817037ad933c4d2b |
completed | March 27, 2026, 7:10 a.m. |
Created at: March 22, 2026, 4:32 p.m.