Triple
T6925431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Svaneke |
E160294
|
entity |
| Predicate | municipalReformYear |
P38054
|
FINISHED |
| Object | 2003 |
—
|
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: 2003 | Statement: [Svaneke, municipalReformYear, 2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: municipalReformYear Context triple: [Svaneke, municipalReformYear, 2003]
-
A.
municipalityReform
chosen
Indicates a formal reorganization or restructuring of a municipality’s administrative boundaries, governance, or status.
-
B.
timeOfMajorReforms
Indicates the specific time period during which significant reforms or major changes took place.
-
C.
unitaryAuthoritySince
Indicates the point in time from which an entity has held the status or role of a unitary authority.
-
D.
municipalityEstablished
Indicates that a municipality was officially created or founded at a specific point in time.
-
E.
yearEnteredIntoForce
Indicates the year in which an agreement, law, treaty, or similar instrument officially became legally effective or operational.
- 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_69c6884d350081908d8a970e4d40ad78 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6da18b6388190947dfc1eb9e5d382 |
completed | March 27, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bb577c81908ee8b415b4281f3d |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:26 p.m.