Triple

T5902270
Position Surface form Disambiguated ID Type / Status
Subject Kesteven E131255 entity
Predicate existedAsAdministrativeCountyFrom P67228 FINISHED
Object 1889 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: 1889 | Statement: [Kesteven, existedAsAdministrativeCountyFrom, 1889]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: existedAsAdministrativeCountyFrom
Context triple: [Kesteven, existedAsAdministrativeCountyFrom, 1889]
  • A. existedAsCountyUntil
    Indicates that an entity functioned with the status or designation of a county up to a specified end date or time period.
  • B. historicCountyAbolishedAsAdministrativeUnit
    Indicates that a historic county ceased to function as an official administrative unit.
  • C. hasHistoricCountyStatusSince
    Indicates that an entity has held the legal or recognized status of a historic county starting from a specified point in time.
  • D. formerAdministrativeCountyIncludes
    Indicates that a geographic area was once part of, or contained within, the boundaries of a former administrative county.
  • E. hasModernAdministrativeCounty
    Indicates that an entity is located within or associated with a specific modern administrative county as defined by current governmental boundaries.
  • F. None of above. chosen

Provenance (4 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_69c0085864a88190a569c05ff7d65f29 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c0400f1af881908d376ea4793f6dea completed March 22, 2026, 7:16 p.m.
PD Predicate disambiguation batch_69c0334dc8248190b7394dcece362d52 completed March 22, 2026, 6:22 p.m.
PDg Predicate description generation batch_69c0400dbec08190b2ef73689b2c0c31 completed March 22, 2026, 7:16 p.m.
Created at: March 22, 2026, 3:58 p.m.