Triple

T9501432
Position Surface form Disambiguated ID Type / Status
Subject Durham Region E229148 entity
Predicate censusDivisionType P88971 FINISHED
Object regional municipality 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: regional municipality | Statement: [Durham Region, censusDivisionType, regional municipality]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: censusDivisionType
Context triple: [Durham Region, censusDivisionType, regional municipality]
  • A. censusSubdivisionType
    Indicates the specific administrative or geographic category assigned to a census subdivision (e.g., city, town, rural area) within a census system.
  • B. sharesFederalDivisionType
    Indicates that two entities are associated with the same type of federal administrative or electoral division.
  • C. countrySubdivisionType
    Indicates the specific type or category of an administrative or territorial subdivision within a country (e.g., state, province, region).
  • D. typeOfDistrict
    Indicates the specific category or classification to which a given district belongs.
  • E. politicalSubdivisionType
    Indicates the specific category or level of governmental or administrative division that characterizes a political subdivision.
  • 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_69ca84753660819098e8d416e89e26ae completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd983d4b708190a4dfef1246986a26 completed April 1, 2026, 10:12 p.m.
PD Predicate disambiguation batch_69cca5651a588190a3cfebe249a223e5 completed April 1, 2026, 4:56 a.m.
PDg Predicate description generation batch_69cca8c6b0f081908334d6c7cf80e03c completed April 1, 2026, 5:10 a.m.
Created at: March 30, 2026, 7:57 p.m.