Triple
T8534249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nissewaard |
E202035
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object | Abbenbroek |
E227871
|
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: Abbenbroek | Statement: [Nissewaard, hasSettlement, Abbenbroek]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Abbenbroek Context triple: [Nissewaard, hasSettlement, Abbenbroek]
-
A.
Abbenbroek
chosen
Abbenbroek is a small village in the Dutch province of South Holland, known for its rural character and historic church.
-
B.
Nieuwendijk
Nieuwendijk is one of Amsterdam’s oldest and busiest shopping streets, running through the historic city center near Dam Square.
-
C.
Bullewijk
Bullewijk is a small waterway and urban canal in Amsterdam’s southeastern area, integrated into the city’s network of rivers and canals.
-
D.
Schipbeek
Schipbeek is a small river in the eastern Netherlands that flows through the provinces of Overijssel and Gelderland before joining the IJssel.
-
E.
Breukelen
Breukelen is a Dutch town in the province of Utrecht, known as the namesake of Brooklyn in New York City.
- 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_69ca832355b08190b8b6a4ab4a4a3554 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe6a0ccd4819097b41d0dfb1c5018 |
completed | March 31, 2026, 3:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d05bdc87fc8190a5ae0883742cb08c |
completed | April 4, 2026, 12:31 a.m. |
Created at: March 30, 2026, 6:17 p.m.