Triple
T10373931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moss municipality |
E244452
|
entity |
| Predicate | municipalNumber |
P23997
|
FINISHED |
| Object | 3002 |
—
|
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: 3002 | Statement: [Moss municipality, municipalNumber, 3002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: municipalNumber Context triple: [Moss municipality, municipalNumber, 3002]
-
A.
municipalKey
chosen
Indicates a unique identifier that links an entity to a specific municipality within an administrative or geographic system.
-
B.
hasMunicipalDistrictNumber
Indicates that a municipality or local administrative unit is assigned a specific district number within its municipal structure.
-
C.
formerMunicipalityNumber
Indicates that an entity was previously assigned a specific official municipality identification number before administrative or territorial changes.
-
D.
municipality
Indicates that one entity is a municipality (a local administrative unit) in which the other entity is located or which it governs.
-
E.
mainMunicipality
Indicates that one municipality serves as the primary or central administrative municipality associated with another entity or area.
- 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9804e708190b15f5d38cac9c4c1 |
completed | April 7, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69d4dface5508190a7b42f01ad0a19a2 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 12:02 p.m.