Triple
T17812257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Katwijk (Cuijk) |
E444739
|
entity |
| Predicate | formerlyInMunicipality |
P5557
|
FINISHED |
| Object | Cuijk |
—
|
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: Cuijk | Statement: [Katwijk (Cuijk), formerlyInMunicipality, Cuijk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerlyInMunicipality Context triple: [Katwijk (Cuijk), formerlyInMunicipality, Cuijk]
-
A.
formerlyInDistrict
Indicates that an entity was once located in or part of a particular district, but is no longer within that district.
-
B.
formerMunicipalityOf
chosen
Indicates that an entity was previously an independent municipality that has since been merged into or replaced by the referenced municipality.
-
C.
formerMunicipalityType
Indicates that an entity was previously classified as a specific type of municipality but no longer holds that municipal status.
-
D.
previousMunicipalityNameVariant
Indicates that an entity had a different municipality name in the past, specifying a former variant of its municipal designation.
-
E.
wasMunicipalityIn
Indicates that an entity previously held the status of a municipality within a specified administrative or territorial unit.
- F. None of above.
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_69d8b9f0de78819099395b14db75a8a6 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4887c63608190b29a407cabff0bc5 |
completed | April 19, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:14 a.m.