Triple
T19933161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wolfram Burgard |
E479106
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Burgard |
—
|
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: Burgard | Statement: [Wolfram Burgard, familyName, Burgard]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Burgard Context triple: [Wolfram Burgard, familyName, Burgard]
-
A.
Burgard
chosen
Burgard is a German surname borne by individuals such as the computer scientist Wolfram Burgard.
-
B.
Schleye
Schleye is a variant spelling of the surname Schley, which is of German origin.
-
C.
Leiningen
Leiningen is a popular build automation and project management tool for the Clojure programming language, used to manage dependencies, run tasks, and streamline development workflows.
-
D.
Heideck
Heideck is a small market town in the Weißenburg-Gunzenhausen district of Bavaria, Germany, known for its rural character and regional historical charm.
-
E.
Heideck
Heideck was a notable Philhellene, remembered for his support of the Greek cause during the Greek War of Independence.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a1553348190a6c4004d3f9a57c5 |
completed | April 20, 2026, 4:53 p.m. |
Created at: April 10, 2026, 1:53 p.m.