Triple
T20087010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubert Bruls |
E496161
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Bruls |
—
|
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: Bruls | Statement: [Hubert Bruls, familyName, Bruls]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bruls Context triple: [Hubert Bruls, familyName, Bruls]
-
A.
Bruls
chosen
Bruls is a Dutch surname most notably borne by Hubert Bruls, a Dutch politician and long-serving mayor of Nijmegen.
-
B.
Zwanenburg
Zwanenburg is a village in North Holland, Netherlands, situated near Amsterdam and known as a suburban residential community within the Haarlemmermeer municipality.
-
C.
Bredius
Bredius is a Dutch surname most notably associated with Abraham Bredius, a prominent art historian and expert on Dutch Golden Age painting.
-
D.
Rozenburg
Rozenburg is a town in the western Netherlands that forms part of the heavily industrialized and port-dominated region of South Holland.
-
E.
Rozenburg
Rozenburg is a village in the municipality of Haarlemmermeer in the province of North Holland, Netherlands.
- 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_69da626eee3881909f3454986d4a6511 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6655ba40c8190adea0e271a1249cf |
completed | April 20, 2026, 5:41 p.m. |
Created at: April 11, 2026, 11:12 p.m.