Triple
T8960756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herzberg am Harz |
E213995
|
entity |
| Predicate | hasNearbyTown |
P3883
|
FINISHED |
| Object | Göttingen |
E25610
|
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: Göttingen | Statement: [Herzberg am Harz, hasNearbyTown, Göttingen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Göttingen Context triple: [Herzberg am Harz, hasNearbyTown, Göttingen]
-
A.
Göttingen
chosen
Göttingen is a historic university city in Lower Saxony, Germany, renowned for its prestigious Georg-August University and contributions to science and mathematics.
-
B.
Darmstadt
Darmstadt is a city in the German state of Hesse known for its historical ties to the Grand Duchy of Hesse and its role as a center of science, technology, and Art Nouveau culture.
-
C.
Greifswald
Greifswald is a historic Hanseatic university city in northeastern Germany, located near the Baltic Sea.
-
D.
Heidelberg
Heidelberg is a suburb of Melbourne, Australia, known for its historic role in Australian Impressionism and its location along the Yarra River.
-
E.
Heidelberg
Heidelberg is a South African town known for its historical significance and role as a regional service and commercial center.
- 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_69ca839cd6008190a1546a701a56710c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6746fbf88190aba658b4b9c2e4b0 |
completed | April 1, 2026, 12:31 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0772ba2808190b8b7948a09b8dee5 |
completed | April 4, 2026, 2:27 a.m. |
Created at: March 30, 2026, 7 p.m.