Triple
T15842252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oschersleben Motorsport Arena |
E384127
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Oschersleben |
E595764
|
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: Oschersleben | Statement: [Oschersleben Motorsport Arena, locatedIn, Oschersleben]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oschersleben Context triple: [Oschersleben Motorsport Arena, locatedIn, Oschersleben]
-
A.
Oschersleben
chosen
Oschersleben is a town in the German state of Saxony-Anhalt, known for its motorsport race track Motorsport Arena Oschersleben.
-
B.
Dennewitz
Dennewitz is a village in Brandenburg, Germany, historically notable as the site of a major 1813 battle during the Napoleonic Wars.
-
C.
Aschersleben
Aschersleben is a historic town in the German state of Saxony-Anhalt, known as one of the oldest documented cities in central Germany.
-
D.
Mahlsdorf
Mahlsdorf is a locality in the borough of Marzahn-Hellersdorf in eastern Berlin, Germany, known for its residential character and historic village center.
-
E.
Oranienburg
Oranienburg is a town in Brandenburg, Germany, historically known as the site of the Nazi Sachsenhausen concentration camp.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e142e88ff08190a1035269e8fdaa6a |
completed | April 16, 2026, 8:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0067948b308190a434cdf1d45ebef4 |
completed | May 10, 2026, 11:10 a.m. |
Created at: April 10, 2026, 4:50 a.m.