Triple
T3450566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zuid-Beveland |
E72782
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object | Kruiningen |
E322976
|
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: Kruiningen | Statement: [Zuid-Beveland, hasSettlement, Kruiningen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kruiningen Context triple: [Zuid-Beveland, hasSettlement, Kruiningen]
-
A.
Ridderkerk
Ridderkerk is a town and municipality in the western Netherlands, situated near Rotterdam in the province of South Holland.
-
B.
Soestdijk
Soestdijk is a village in the Netherlands known for its historic royal residence, Soestdijk Palace.
-
C.
Begijnhof
Begijnhof is a historic, secluded courtyard in central Amsterdam known for its preserved medieval houses and former beguine community.
-
D.
’s-Heer Arendskerke
chosen
’s-Heer Arendskerke is a small village in the Dutch province of Zeeland, known for its rural character and historic church.
-
E.
Gilze en Rijen
Gilze en Rijen is a municipality and town in the southern Netherlands known for its proximity to Breda and its military air base.
- 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_69ad85b05c848190b7a28ceec2bd7b74 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adba7324508190b07943cec3ecdb59 |
completed | March 8, 2026, 6:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b367fc4e8c81909fb57634113369fa |
completed | March 13, 2026, 1:27 a.m. |
Created at: March 8, 2026, 3:16 p.m.