Triple
T23226039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlin–Lehrte railway corridor |
E581014
|
entity |
| Predicate | connects |
P390
|
FINISHED |
| Object | Lehrte |
—
|
NE NERFINISHED |
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: Lehrte | Statement: [Berlin–Lehrte railway corridor, connects, Lehrte]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lehrte Context triple: [Berlin–Lehrte railway corridor, connects, Lehrte]
-
A.
Lehrte
chosen
Lehrte is a town in Lower Saxony, Germany, located east of Hanover and known historically for its railway junction and agricultural surroundings.
-
B.
Uelzen
Uelzen is a small town in Lower Saxony, Germany, known for its distinctive Hundertwasser-designed railway station and its role as a regional transport hub.
-
C.
Helmstedt
Helmstedt is a historic town in Lower Saxony, Germany, known for its medieval architecture and former university.
-
D.
Northeim
Northeim is a town in Lower Saxony, Germany, known for its medieval old town and location in the Leine River valley.
-
E.
Neubrandenburg
Neubrandenburg is a historic city in northeastern Germany known for its well-preserved medieval brick Gothic architecture and distinctive city wall with multiple gate towers.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e246043c48819089bae72c9a9c306c |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f1922e2d2c81908c0f3fa5df8a5c58 |
completed | April 29, 2026, 5:07 a.m. |
Created at: April 17, 2026, 4:08 p.m.