Triple
T12116577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grootegast |
E288576
|
entity |
| Predicate | formerMunicipalityCode |
P83825
|
FINISHED |
| Object | 0015 |
—
|
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: 0015 | Statement: [Grootegast, formerMunicipalityCode, 0015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerMunicipalityCode Context triple: [Grootegast, formerMunicipalityCode, 0015]
-
A.
formerMunicipalityNumber
chosen
Indicates that an entity was previously assigned a specific official municipality identification number before administrative or territorial changes.
-
B.
formerMunicipalityOf
Indicates that an entity was previously an independent municipality that has since been merged into or replaced by the referenced municipality.
-
C.
formerINSEECode
Indicates that an entity was previously identified by a different INSEE code before being assigned its current one.
-
D.
previousMunicipalityNameVariant
Indicates that an entity had a different municipality name in the past, specifying a former variant of its municipal designation.
-
E.
formerNameOfDistrict
Indicates that one district previously had a different official name, which is the value linked by this predicate.
- 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_69d6ab4a5c448190a110d1273314b21a |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9164ada5081908676bd9e5947268a |
completed | April 10, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69d9150497408190921334d21503375a |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:49 p.m.