Triple
T6624515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schweinfurt region |
E149760
|
entity |
| Predicate | containsTown |
P847
|
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: [Schweinfurt region, containsTown, Heidenfeld]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heidenfeld Context triple: [Schweinfurt region, containsTown, 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.
Sennfeld
Sennfeld is a municipality in the Schweinfurt district of Bavaria, Germany, known for its traditional Franconian character and proximity to the city of Schweinfurt.
-
D.
Ochsenfeld
Ochsenfeld is a German surname most notably borne by physicist Robert Ochsenfeld, known for his work on superconductivity.
-
E.
Pennenfeld
Pennenfeld is a residential subdistrict of the Bonn borough of Bad Godesberg 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_69c687ed8a9c81908bb671717cb192ef |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6af7fc054819099a2e58cefd8fed7 |
completed | March 27, 2026, 4:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c72f7450dc8190881a9347b8b9475f |
completed | March 28, 2026, 1:31 a.m. |
Created at: March 27, 2026, 1:58 p.m.