Triple

T38528320
Position Surface form Disambiguated ID Type / Status
Subject County of Clwyd E923289 entity
Predicate containedHistoricCountyPart P103366 FINISHED
Object historic county of Flintshire E812580 NE 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 Flintshire | Statement: [County of Clwyd, containedHistoricCountyPart, historic county of Flintshire]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: containedHistoricCountyPart
Context triple: [County of Clwyd, containedHistoricCountyPart, historic county of Flintshire]
  • A. historicCountyPart chosen
    Indicates that one entity forms a constituent part or subdivision of a historic county.
  • B. hasAssociatedHistoricCounty
    Indicates that an entity is linked to a specific historic county with which it is geographically or administratively associated.
  • C. coversHistoricCounty
    Indicates that one entity geographically encompasses the area of a historic county.
  • D. formerAdministrativeCountyIncludes
    Indicates that a geographic area was once part of, or contained within, the boundaries of a former administrative county.
  • 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 (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_69f76ea8f6348190a5c03fb6292bbee3 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_6a02206665508190ae2324d253ccf377 completed May 11, 2026, 6:31 p.m.
NED1 Entity disambiguation (via context triple) batch_6a41d66edc0c8190b61ec09ef2255627 completed June 29, 2026, 2:20 a.m.
PD Predicate disambiguation batch_6a021fdc6e54819082847bedd97a680b completed May 11, 2026, 6:28 p.m.
Created at: May 3, 2026, 4:32 p.m.