Triple

T4982934
Position Surface form Disambiguated ID Type / Status
Subject Aucklander E111930 entity
Predicate hasPluralForm P5088 FINISHED
Object Aucklanders E111930 NE 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: Aucklanders | Statement: [Aucklander, hasPluralForm, Aucklanders]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aucklanders
Context triple: [Aucklander, hasPluralForm, Aucklanders]
  • A. Aucklander chosen
    An Aucklander is a resident or native of Auckland, the largest city in New Zealand.
  • B. Auckland
    Auckland is a major New Zealand metropolis known for its harbors, multicultural population, and role as the country’s primary economic and transport hub.
  • C. Christchurch
    Christchurch is a historic coastal town in Dorset, England, known for its medieval priory, natural harbour, and proximity to the New Forest.
  • D. Māngere
    Māngere is a suburb of Auckland, New Zealand, known for its proximity to Auckland Airport and its culturally diverse community.
  • E. Pukekohe
    Pukekohe is a town in the Auckland Region of New Zealand, known for its rich agricultural land and motor racing circuit.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69bd441adc208190b70a033a0741d01e completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd725489bc81908f660332e25f29cf completed March 20, 2026, 4:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69be8a13f5448190a49f914d1ba49a7a completed March 21, 2026, 12:07 p.m.
Created at: March 20, 2026, 1:33 p.m.