Triple
T12989084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doetinchem |
E321848
|
entity |
| Predicate | municipalityFormed |
P23872
|
FINISHED |
| Object | 1 January 1920 |
—
|
LITERAL 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: 1 January 1920 | Statement: [Doetinchem, municipalityFormed, 1 January 1920]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: municipalityFormed Context triple: [Doetinchem, municipalityFormed, 1 January 1920]
-
A.
municipalityEstablished
chosen
Indicates that a municipality was officially created or founded at a specific point in time.
-
B.
hasMunicipalFormation
Indicates that an administrative or territorial unit is organized into, or associated with, a specific municipal formation as its local self-governing structure.
-
C.
formedMunicipalityWith
Indicates that two or more entities combined or were merged to create a single municipality.
-
D.
formerMunicipalityOf
Indicates that an entity was previously an independent municipality that has since been merged into or replaced by the referenced municipality.
-
E.
municipality
Indicates that one entity is a municipality (a local administrative unit) in which the other entity is located or which it governs.
- 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_69d8076479b8819090afce3591939cdf |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97f2a71a0819098bb6cf8a4b2208a |
completed | April 10, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69d97dbdd94c8190ac4bbecca02dc77b |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:42 p.m.