Triple
T13402885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brugg District |
E319876
|
entity |
| Predicate | hasHistoricTown |
P847
|
FINISHED |
| Object | Brugg |
E270538
|
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: Brugg | Statement: [Brugg District, hasHistoricTown, Brugg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Brugg Context triple: [Brugg District, hasHistoricTown, Brugg]
-
A.
Brugg
chosen
Brugg is a historic Swiss town in the canton of Aargau, known for its medieval heritage and strategic location near the confluence of the Aare, Reuss, and Limmat rivers.
-
B.
Maasbracht
Maasbracht is a town in the Dutch province of Limburg, known as an inland port and industrial center along the River Meuse.
-
C.
Beringen
Beringen is a city and municipality in the Belgian province of Limburg, known for its coal mining heritage and the be-MINE industrial heritage site.
-
D.
Turnhout
Turnhout is a historic city in northern Belgium known for its playing card industry, cultural heritage, and role as a regional center in the Kempen area.
-
E.
Bruges
Bruges is a historic Belgian city renowned for its well-preserved medieval architecture, picturesque canals, and rich artistic heritage.
- 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_69d806b943cc8190b6af624d385d7e12 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbae4982e0819087a9fcb2fa88541f |
completed | April 12, 2026, 2:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f75475d7648190b050e44a5312d13d |
completed | May 3, 2026, 1:58 p.m. |
Created at: April 9, 2026, 9:34 p.m.