Triple

T36846070
Position Surface form Disambiguated ID Type / Status
Subject Tuapeka E910549 entity
Predicate formerElectorate P85908 FINISHED
Object Tuapeka (New Zealand electorate) 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: Tuapeka (New Zealand electorate) | Statement: [Tuapeka, formerElectorate, Tuapeka (New Zealand electorate)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: formerElectorate
Context triple: [Tuapeka, formerElectorate, Tuapeka (New Zealand electorate)]
  • A. previousElectorate chosen
    Indicates that one electorate served as the earlier or former electoral district associated with another electorate.
  • B. wasElectorate
    Indicates that one entity functioned as the electorate (voting body or constituency) for another entity, such as an office, position, or representative.
  • C. electoralBodyPreviouslyKnownAs
    Indicates that an electoral body was formerly known by a different official name before being renamed or reconstituted.
  • D. successorElectorate
    Indicates that one electorate directly follows and replaces another in an official sequence or succession.
  • E. elector
    Indicates a relationship where one entity has the right or role to choose or vote for another entity in an election or selection process.
  • 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_69f76e7f65a881908651b702da592b6d completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_6a00b6199c348190b1e90375f737d026 completed May 10, 2026, 4:45 p.m.
PD Predicate disambiguation batch_6a00b5169a7881909a07167c4188731f completed May 10, 2026, 4:40 p.m.
Created at: May 3, 2026, 4:13 p.m.