Triple

T30131083
Position Surface form Disambiguated ID Type / Status
Subject Abingdon Rural District E765846 entity
Predicate borderedUrbanDistrict P107921 FINISHED
Object Abingdon Municipal Borough NE NERFINISHED

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: Abingdon Municipal Borough | Statement: [Abingdon Rural District, borderedUrbanDistrict, Abingdon Municipal Borough]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: borderedUrbanDistrict
Context triple: [Abingdon Rural District, borderedUrbanDistrict, Abingdon Municipal Borough]
  • A. isBorderDistrict
    Indicates that a district is located along and directly borders the boundary of a larger administrative region or country.
  • B. borderIncludesUrbanAreaPair
    Indicates that a border region encompasses or connects a specific pair of urban areas.
  • C. borderingLocalGovernmentArea chosen
    Indicates that one local government area shares a common boundary with another local government area.
  • D. isUrbanBoundaryFor
    Indicates that something serves as the defined outer limit or edge that separates an urban area from surrounding non-urban or differently zoned areas.
  • E. hasArrondissementBoundary
    Indicates that one arrondissement’s boundary is shared with, or directly borders, another arrondissement.
  • 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_69f22477d1a081908df2b7e6ed16859d completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69fe610e1f6881908f10070ba64643cf completed May 8, 2026, 10:17 p.m.
PD Predicate disambiguation batch_69fe604c6c008190ad659e9b9fa82f7b completed May 8, 2026, 10:14 p.m.
Created at: April 29, 2026, 7:15 p.m.