Triple
T4730189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishopric of Roermond |
E104985
|
entity |
| Predicate | seat |
P75
|
FINISHED |
| Object | Roermond |
E461071
|
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: Roermond | Statement: [Bishopric of Roermond, seat, Roermond]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Roermond Context triple: [Bishopric of Roermond, seat, Roermond]
-
A.
Roermond
chosen
Roermond is a historic city in the southeastern Netherlands known for its medieval architecture, prominent churches, and large designer outlet shopping center.
-
B.
Venlo
Venlo is a historic city in the southeastern Netherlands, located near the German border on the river Meuse and known as a regional economic and logistics hub.
-
C.
Gorinchem
Gorinchem is a historic fortified city in the Netherlands known for its well-preserved city walls and picturesque old town.
-
D.
Heerlen
Heerlen is a city in the southeastern Netherlands known for its mining history and modernist architecture, located in the province of Limburg.
-
E.
Helmond
Helmond is a city in the southern Netherlands known for its historic castle, industrial heritage, and location near Eindhoven in the province of North Brabant.
- 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_69bd43ee52048190b81a4f066534ffb3 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64629bc081908754aa8a2630091f |
completed | March 20, 2026, 3:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c67c2b4f188190a78b591674040060 |
completed | March 27, 2026, 12:46 p.m. |
Created at: March 20, 2026, 1:19 p.m.