Triple
T22748742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamme |
E562631
|
entity |
| Predicate | hasSubdivision |
P747
|
FINISHED |
| Object | Hamme (town) |
—
|
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: Hamme (town) | Statement: [Hamme, hasSubdivision, Hamme (town)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hamme (town) Context triple: [Hamme, hasSubdivision, Hamme (town)]
-
A.
Hamme
chosen
Hamme is a municipality in East Flanders, Belgium, known for its location along the Scheldt River and its blend of residential areas and natural landscapes.
-
B.
Hamme-Mille
Hamme-Mille is a village in Walloon Brabant, Belgium, forming part of the municipality of Beauvechain.
-
C.
Schmieheim
Schmieheim is a village in the Ortenau district of Baden-Württemberg, Germany, that forms a local subdivision of the municipality of Kippenheim.
-
D.
Hemmingen
Hemmingen is a municipality in Germany, known as a small town that engages in international town twinning partnerships.
-
E.
Hammelburg
Hammelburg is a historic town in northern Bavaria, Germany, known as one of the country’s oldest wine-growing communities.
- 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_69e24551ec7881909a9c924dbea155f6 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f179b822988190b5368ac1f4e1d70a |
completed | April 29, 2026, 3:23 a.m. |
Created at: April 17, 2026, 3:24 p.m.