Triple

T2268362
Position Surface form Disambiguated ID Type / Status
Subject Cudham E50599 entity
Predicate hasHistoricCountyAffiliation P1069 FINISHED
Object historic county of Kent 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: historic county of Kent | Statement: [Cudham, hasHistoricCountyAffiliation, historic county of Kent]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHistoricCountyAffiliation
Context triple: [Cudham, hasHistoricCountyAffiliation, historic county of Kent]
  • 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. hasHistoricCountySeat
    Indicates that an administrative region historically had its county government or main county offices located in a particular settlement or city.
  • C. hasHistoricCountyNumber
    Indicates that an entity is associated with a specific identifier corresponding to its historic county designation.
  • D. historicalCounty chosen
    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.
  • E. hasHistoricRegistrationCountyStatus
    Indicates that an entity holds or has held official historic registration status within a particular county.
  • 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_69a88b05910c8190a9a2b1ff230c85f9 completed March 4, 2026, 7:41 p.m.
NER Named-entity recognition batch_69abc2ea65288190bc8644a07a11dfa9 completed March 7, 2026, 6:17 a.m.
PD Predicate disambiguation batch_69abbdb592588190ac1ef5e8c54575b1 completed March 7, 2026, 5:55 a.m.
Created at: March 4, 2026, 7:48 p.m.