Triple

T36846071
Position Surface form Disambiguated ID Type / Status
Subject Tuapeka E910549 entity
Predicate electorateExistenceStart P42150 FINISHED
Object 1871 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: 1871 | Statement: [Tuapeka, electorateExistenceStart, 1871]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: electorateExistenceStart
Context triple: [Tuapeka, electorateExistenceStart, 1871]
  • A. electorateEstablished chosen
    Indicates that an electorate or voting district has been formally created or brought into existence.
  • B. electorateEstablishedFor
    Indicates that a particular electorate or voting district has been created or designated to serve and represent a specific entity (such as a body, office, or jurisdiction).
  • C. electorateEstablishedBy
    Indicates that an electorate (voting district or body of voters) was created or formally brought into existence by a specific authority, law, or founding action.
  • D. electorateUntil
    Indicates that an entity serves as an electorate for another entity up to, but not beyond, a specified point in time.
  • E. electorateCreatedFrom
    Indicates that a particular electorate or voting district was formed by dividing, merging, or otherwise deriving it from another electoral unit.
  • 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_69ff7eb7189c81909a8f73fbc4c48e02 completed May 9, 2026, 6:36 p.m.
PD Predicate disambiguation batch_69ff7e54e11081908fb5ce10c5aa7b53 completed May 9, 2026, 6:35 p.m.
Created at: May 3, 2026, 4:13 p.m.