Triple

T11699529
Position Surface form Disambiguated ID Type / Status
Subject Ponsonby family E278083 entity
Predicate hasAncestralSurname P36967 FINISHED
Object Ponsonby E922052 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: Ponsonby | Statement: [Ponsonby family, hasAncestralSurname, Ponsonby]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ponsonby
Context triple: [Ponsonby family, hasAncestralSurname, Ponsonby]
  • A. Ponsonby chosen
    Ponsonby is an English and Irish aristocratic surname historically associated with prominent political and social figures.
  • B. Māngere
    Māngere is a suburb of Auckland, New Zealand, known for its proximity to Auckland Airport and its culturally diverse community.
  • C. Mount Roskill
    Mount Roskill is a suburban area and volcanic cone in Auckland, New Zealand, known for its diverse community and residential character.
  • D. Pukekohe
    Pukekohe is a town in the Auckland Region of New Zealand, known for its rich agricultural land and motor racing circuit.
  • E. Mount Albert
    Mount Albert is a small rural community in the town of East Gwillimbury, Ontario, known for its village character and surrounding farmland.
  • 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_69d6aafe02d881909900d54ad7d4af84 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a47df68c81908a91919a69b4880d completed April 10, 2026, 7:19 a.m.
NED1 Entity disambiguation (via context triple) batch_69ef833084988190b5004c93f68dc628 completed April 27, 2026, 3:39 p.m.
Created at: April 8, 2026, 9:40 p.m.