Triple

T23875391
Position Surface form Disambiguated ID Type / Status
Subject Christchurch Central E592849 entity
Predicate hasElectorateClassification P15379 FINISHED
Object urban 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: urban | Statement: [Christchurch Central, hasElectorateClassification, urban]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasElectorateClassification
Context triple: [Christchurch Central, hasElectorateClassification, urban]
  • A. hasElectorate
    Indicates that a political representative, office, or governing body is associated with and serves a specific group of voters or electoral district.
  • B. hasParliamentaryElectorate
    Indicates that a political or administrative entity is represented by, or belongs to, a specific parliamentary electoral district.
  • C. hasElectorateCode
    Indicates that an electorate (voting district) is associated with a specific identifying code.
  • D. electorateCategory chosen
    Indicates the classification of an electorate or voter group into a specific category based on defined electoral or demographic criteria.
  • E. hasElectorateProfile
    Indicates that an entity is associated with a specific electorate-related profile describing its voting or demographic characteristics.
  • 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_69e25d23a5c88190ae3999c70ca15e08 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1cc012974819090b34aad6a230f81 completed April 29, 2026, 9:14 a.m.
PD Predicate disambiguation batch_69f1614a65a88190bde1efb368a151e4 completed April 29, 2026, 1:39 a.m.
Created at: April 17, 2026, 8:15 p.m.