Triple
T6316752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TSV Kolbermoor |
E141634
|
entity |
| Predicate | basedIn |
P40
|
FINISHED |
| Object | Kolbermoor |
E141634
|
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: Kolbermoor | Statement: [TSV Kolbermoor, basedIn, Kolbermoor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kolbermoor Context triple: [TSV Kolbermoor, basedIn, Kolbermoor]
-
A.
Kolbermoor
chosen
Kolbermoor is a small Bavarian town in southern Germany, known as the birthplace of footballer Bastian Schweinsteiger.
-
B.
Seebruck
Seebruck is a Bavarian lakeside village and popular holiday resort on the northern shore of Lake Chiemsee in southern Germany.
-
C.
Lochau
Lochau is a locality in Germany historically noted as the place where the influential Reformation-era prince Frederick the Wise died.
-
D.
Bürmoos
Bürmoos is a small Austrian municipality located in the state of Salzburg, known for its residential character and proximity to the city of Salzburg.
-
E.
Hallbergmoos
Hallbergmoos is a municipality in Bavaria, Germany, known for hosting major aerospace and technology companies near Munich.
- 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_69c008d13b8c8190be47d896eb735605 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064c25530819080b29e0029175c00 |
completed | March 22, 2026, 9:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6040714988190abbbadb4039966ef |
completed | March 27, 2026, 4:13 a.m. |
Created at: March 22, 2026, 4:29 p.m.