Triple
T12359539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael von Faulhaber |
E294697
|
entity |
| Predicate | birthPlace |
P1
|
FINISHED |
| Object | Heidenfeld |
E294697
|
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: Heidenfeld | Statement: [Michael von Faulhaber, birthPlace, Heidenfeld]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heidenfeld Context triple: [Michael von Faulhaber, birthPlace, Heidenfeld]
-
A.
Heidenfeld
chosen
Heidenfeld is a village in Bavaria, Germany, known as the birthplace of Cardinal Michael von Faulhaber.
-
B.
Heiderhof
Heiderhof is a residential subdistrict of the Bonn borough Bad Godesberg in western Germany.
-
C.
Todenfeld
Todenfeld is a village and district of the town of Rheinbach in the Rhein-Sieg-Kreis region of North Rhine-Westphalia, Germany.
-
D.
Hellefeld
Hellefeld is a village and district within the town of Sundern in the Hochsauerland region of North Rhine-Westphalia, Germany.
-
E.
Hupfeld
Hupfeld is a German surname most notably borne by American songwriter Herman Hupfeld, composer of "As Time Goes By."
- 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_69d6ab6d8a4081908636601e69ddf262 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f90201481909359416b8b9f7871 |
completed | April 10, 2026, 6:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f655608a0c81908002f9d79d017ded |
completed | May 2, 2026, 7:49 p.m. |
Created at: April 8, 2026, 9:54 p.m.