Triple
T16423399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finnmark |
E398878
|
entity |
| Predicate | dissolvedAsCountyOn |
P52130
|
FINISHED |
| Object | 2020-01-01 |
—
|
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: 2020-01-01 | Statement: [Finnmark, dissolvedAsCountyOn, 2020-01-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dissolvedAsCountyOn Context triple: [Finnmark, dissolvedAsCountyOn, 2020-01-01]
-
A.
existedAsCountyUntil
chosen
Indicates that an entity functioned with the status or designation of a county up to a specified end date or time period.
-
B.
dissolvedOrAbolishedBy
Indicates that an entity (such as an organization, institution, or legal body) ceased to exist as a result of a specific dissolving or abolishing action carried out by another entity or authority.
-
C.
dissolvedOrAbolished
Indicates that an organization, institution, or formal entity has been officially terminated, disbanded, or ceased to exist.
-
D.
hasFormerCounty
Indicates that an entity was previously part of, or administered by, a particular county in the past but no longer is.
-
E.
wasDissolvedAfter
Indicates that one entity ceased to exist or operate at a later point in time than another entity’s dissolution.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e328f911b88190b19de52a1f700af8 |
completed | April 18, 2026, 6:47 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:09 a.m.