Triple
T30545366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noormarkku |
E777398
|
entity |
| Predicate | municipalityStatusEnded |
P138390
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Noormarkku, municipalityStatusEnded, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: municipalityStatusEnded Context triple: [Noormarkku, municipalityStatusEnded, 2010]
-
A.
hasMunicipalStatusUntil
Indicates that an entity possessed municipal status up to, but not beyond, a specified point in time.
-
B.
municipalityStatusGranted
Indicates that an entity has been officially granted the legal status and recognition of a municipality.
-
C.
municipalityStatusAtLocation
Indicates that an entity holds a specific municipal status (e.g., city, town, village) at or within a particular geographic location.
-
D.
previousMunicipalityStatus
Indicates that one municipality previously held a particular municipal status or classification before a change occurred.
-
E.
formerMunicipalityDisestablished
chosen
Indicates that a municipality, which previously existed as an administrative unit, was officially dissolved or ceased to exist at a specific point in time.
- 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_69f2249d183c8190b79937c1768d2163 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 29, 2026, 8:19 p.m.