Triple

T4206592
Position Surface form Disambiguated ID Type / Status
Subject Telemark E93796 entity
Predicate historicCountyStatusEnded P41542 FINISHED
Object 2019-12-31 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: 2019-12-31 | Statement: [Telemark, historicCountyStatusEnded, 2019-12-31]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicCountyStatusEnded
Context triple: [Telemark, historicCountyStatusEnded, 2019-12-31]
  • A. hasHistoricCountyStatusSince
    Indicates that an entity has held the legal or recognized status of a historic county starting from a specified point in time.
  • B. historicCountyAbolishedAsAdministrativeUnit chosen
    Indicates that a historic county ceased to function as an official administrative unit.
  • C. historicCountyPredecessor
    Indicates that one historic county served as a predecessor or earlier form of another historic county in an administrative or territorial succession.
  • D. historicParliamentaryCounty
    Indicates that an entity is (or was) located within, or associated with, a historic parliamentary county as defined for electoral or administrative purposes.
  • E. historicalCounty
    Indicates that an entity was located within or associated with a county as it existed in the past, even if that county’s boundaries or administrative status have since changed.
  • 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_69b3451743608190808f41d17ccf2650 completed March 12, 2026, 10:58 p.m.
NER Named-entity recognition batch_69b34e098da881909a0cc339cc186627 completed March 12, 2026, 11:36 p.m.
PD Predicate disambiguation batch_69b347efd9b08190bb50f82e4e7fe06d completed March 12, 2026, 11:10 p.m.
Created at: March 12, 2026, 11:03 p.m.