Triple
T1135033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Brabant |
E23119
|
entity |
| Predicate | containsCity |
P294
|
FINISHED |
| Object | Breda |
E151867
|
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: Breda | Statement: [North Brabant, containsCity, Breda]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Breda Context triple: [North Brabant, containsCity, Breda]
-
A.
Breda
chosen
Breda is a historic city in the southern Netherlands known for its medieval architecture, former status as a military and political center, and vibrant cultural life.
-
B.
Arnhem
Arnhem is a city in the eastern Netherlands best known as the site of a major World War II battle during Operation Market Garden.
-
C.
Oudenarde
Oudenarde (Oudenaarde) is a historic town in East Flanders, Belgium, known for its medieval architecture, tapestry production, and role in early modern European conflicts.
-
D.
Dendermonde
Dendermonde is a historic city in East Flanders, Belgium, known for its medieval architecture and UNESCO-recognized Ros Beiaard procession.
-
E.
Arnhemmer
An Arnhemmer is a resident or native of the Dutch city of Arnhem in the province of Gelderland.
- 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_69a493ec75988190b63a11bafaec29b4 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bbfffaa48190b2534ff4da3544ce |
completed | March 1, 2026, 10:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ace54f52988190b25c35271721c3ee |
completed | March 8, 2026, 2:56 a.m. |
Created at: March 1, 2026, 7:44 p.m.