Triple
T13026315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gerd Busch |
E326315
|
entity |
| Predicate | hasSurname |
P18
|
FINISHED |
| Object | Busch |
E79827
|
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: Busch | Statement: [Gerd Busch, hasSurname, Busch]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Busch Context triple: [Gerd Busch, hasSurname, Busch]
-
A.
Busch
chosen
Busch is a common German surname borne by numerous notable individuals across fields such as politics, the arts, and industry.
-
B.
Buescher
Buescher is a surname most prominently associated with American stock car racing driver Chris Buescher.
-
C.
Hendrick
Hendrick is a Dutch given name historically borne by figures such as the 17th-century painter Hendrick Cornelisz. van Vliet.
-
D.
Holley
Holley is a surname most notably associated with Alexander Lyman Holley, a prominent 19th-century American engineer and steel industry pioneer.
-
E.
Buck Ford
Buck Ford is the son of famed American country and gospel singer and television host Tennessee Ernie Ford.
- 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_69d8076cc45c81908123123f43e69266 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97efac71881908a21d70c3c6ce099 |
completed | April 10, 2026, 10:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6c11f83d88190bc153dba75db0995 |
completed | May 3, 2026, 3:29 a.m. |
Created at: April 9, 2026, 8:53 p.m.