Triple

T16167762
Position Surface form Disambiguated ID Type / Status
Subject Bledisloe Terminal E392350 entity
Predicate city P40 FINISHED
Object Auckland E18491 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: Auckland | Statement: [Bledisloe Terminal, city, Auckland]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Auckland
Context triple: [Bledisloe Terminal, city, Auckland]
  • A. Auckland chosen
    Auckland is a major New Zealand metropolis known for its harbors, multicultural population, and role as the country’s primary economic and transport hub.
  • B. Wellington
    Wellington is the compact, hilly coastal city at the southern tip of New Zealand’s North Island known for its vibrant arts scene, windy climate, and role as the country’s political and cultural hub.
  • C. Wellington
    Wellington is a regional town in New South Wales, Australia, known for its agricultural surroundings and location near the junction of the Macquarie and Bell rivers.
  • D. Wellington
    Wellington is a market town in Shropshire, England, now part of the borough of Telford and Wrekin.
  • E. Wellington
    Wellington is a small village in Lorain County, Ohio, known for its historic downtown and rural Midwestern character.
  • 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_69d87f1d32208190942e4e499a80c18c completed April 10, 2026, 4:39 a.m.
NER Named-entity recognition batch_69e21eb4ea9c81908806f9771ae80148 completed April 17, 2026, 11:51 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0025f183d88190b269233ff6e65d75 completed May 10, 2026, 6:30 a.m.
Created at: April 10, 2026, 5:02 a.m.