Triple
T16836912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kologha Forest |
E409306
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Stutterheim |
E409303
|
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: Stutterheim | Statement: [Kologha Forest, locatedNear, Stutterheim]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Stutterheim Context triple: [Kologha Forest, locatedNear, Stutterheim]
-
A.
Stutterheim
chosen
Stutterheim is a small town in South Africa’s Eastern Cape province, known for its forestry, agriculture, and scenic setting near the Amathole Mountains.
-
B.
Blatzheim
Blatzheim is a village and district within the town of Kerpen in North Rhine-Westphalia, Germany.
-
C.
Flerzheim
Flerzheim is a village and district of the town of Rheinbach in the Rhein-Sieg-Kreis region of North Rhine-Westphalia, Germany.
-
D.
Stockheim
Stockheim is a village and district of the town of Brackenheim in the Heilbronn district of Baden-Württemberg, Germany.
-
E.
Steindorf
Steindorf is a small municipality in the Bavarian district of Aichach-Friedberg in southern 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b34e080c8190bf7a236205b41db2 |
completed | April 18, 2026, 4:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00bb15c9f48190a4d73bb08a15beb4 |
completed | May 10, 2026, 5:06 p.m. |
Created at: April 10, 2026, 5:23 a.m.