Triple
T7038618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gooi |
E163449
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Bussum |
E556836
|
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: Bussum | Statement: [Gooi, contains, Bussum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bussum Context triple: [Gooi, contains, Bussum]
-
A.
Bussum
chosen
Bussum is a town in the province of North Holland in the Netherlands, historically known as a residential and commuter community near Amsterdam.
-
B.
Breckerfeld
Breckerfeld is a small town in North Rhine-Westphalia, Germany, known for its rural character and location in the hilly, forested region of the Sauerland.
-
C.
Bentheim
Bentheim is a historical county in Lower Saxony, Germany, known for its Reformed Protestant heritage and the former County of Bentheim.
-
D.
Rudolfswerth
Rudolfswerth is the former German name for Novo Mesto, a historic town in southeastern Slovenia known for its medieval heritage and role as a regional cultural center.
-
E.
Barsinghausen
Barsinghausen is a town in Lower Saxony, Germany, located near Hanover and known historically for its mining industry and proximity to the Deister hills.
- 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_69c6885e7c1c8190be32a8f79ab4e0cf |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e223077c819097992089fa83c563 |
completed | March 27, 2026, 8:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c775ac21888190a1adcf86b49b345f |
completed | March 28, 2026, 6:31 a.m. |
Created at: March 27, 2026, 2:36 p.m.