Triple

T17668737
Position Surface form Disambiguated ID Type / Status
Subject Cunninghame E440456 entity
Predicate existedAsLocalGovernmentDistrictFrom P62788 FINISHED
Object 1975 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: 1975 | Statement: [Cunninghame, existedAsLocalGovernmentDistrictFrom, 1975]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: existedAsLocalGovernmentDistrictFrom
Context triple: [Cunninghame, existedAsLocalGovernmentDistrictFrom, 1975]
  • A. localGovernmentDistrictExistedFrom chosen
    Indicates the date or time period when a local government district first came into official existence.
  • B. existedAsAdministrativeCountyFrom
    Indicates that an entity functioned in the status of an administrative county starting from a specified point in time.
  • C. hasLocalGovernmentDistrictHistory
    Indicates that an entity is associated with a record or description of the historical development, changes, or past status of a local government district.
  • D. abolishedAsLocalGovernmentDistrict
    Indicates that a particular local government district has been officially dissolved or terminated as an administrative unit.
  • E. unitaryAuthoritySince
    Indicates the point in time from which an entity has held the status or role of a unitary authority.
  • 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_69d8b9e87e18819087104a44dc4dc5b1 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e46f6723d081908eaa57eef6d70bd0 completed April 19, 2026, 6 a.m.
PD Predicate disambiguation batch_69e3cde007d8819090dd92eea9f022cc completed April 18, 2026, 6:30 p.m.
Created at: April 10, 2026, 9:58 a.m.