Triple
T11375064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bach |
E269444
|
entity |
| Predicate | hasCognate |
P2525
|
FINISHED |
| Object | Bach (Danish surname) |
E269444
|
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: Bach (Danish surname) | Statement: [Bach, hasCognate, Bach (Danish surname)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bach (Danish surname) Context triple: [Bach, hasCognate, Bach (Danish surname)]
-
A.
Bach (Dutch surname)
Bach (Dutch surname) is a family name of Dutch origin, likely derived from a word related to a stream or brook and shared with similar surnames in neighboring Germanic languages.
-
B.
Bachern
Bachern is a small village in Bavaria, Germany, that forms part of the municipality of Inning am Ammersee.
-
C.
Bacher
Bacher is a German-language surname borne by various notable individuals across fields such as science, sports, and the arts.
-
D.
Bach
chosen
Bach is a renowned German surname most famously associated with the Baroque composer Johann Sebastian Bach and his musically prolific family.
-
E.
Bach
Bach is a small locality or district that forms part of the town of Erbach an der Donau in Germany.
- 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_69d6aacca1048190b39dbbc2174616fa |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7ea8e6d44819095f949581421e98e |
completed | April 9, 2026, 6:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e58bdaabd48190ab533c1c7f3b5fd8 |
completed | April 20, 2026, 2:13 a.m. |
Created at: April 8, 2026, 9:33 p.m.