Triple
T18707390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flesberg municipality |
E457406
|
entity |
| Predicate | hasFormerCountyNumber |
P28960
|
FINISHED |
| Object | 06 |
—
|
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: 06 | Statement: [Flesberg municipality, hasFormerCountyNumber, 06]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerCountyNumber Context triple: [Flesberg municipality, hasFormerCountyNumber, 06]
-
A.
hasFormerCounty
Indicates that an entity was previously part of, or administered by, a particular county in the past but no longer is.
-
B.
hasHistoricCountyNumber
chosen
Indicates that an entity is associated with a specific identifier corresponding to its historic county designation.
-
C.
formerMunicipalityNumber
Indicates that an entity was previously assigned a specific official municipality identification number before administrative or territorial changes.
-
D.
previousCounty
Indicates that one county was the immediately preceding county associated with an entity before the current or later county.
-
E.
hasCountyCode
Indicates that an entity is associated with a specific county identified by a standardized county code.
- 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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e567185c648190848ca47498eb56b3 |
completed | April 19, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:50 a.m.