Triple

T5193959
Position Surface form Disambiguated ID Type / Status
Subject Leeton Shire E117222 entity
Predicate hasLocality P7943 FINISHED
Object North Leeton E21140 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: North Leeton | Statement: [Leeton Shire, hasLocality, North Leeton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: North Leeton
Context triple: [Leeton Shire, hasLocality, North Leeton]
  • A. Leeton chosen
    Leeton is a regional agricultural town in the Riverina area of New South Wales, Australia, known for its irrigated farming and food production.
  • B. Kurrajong
    Kurrajong is an electorate of the Australian Capital Territory Legislative Assembly that covers central Canberra and surrounding suburbs.
  • C. Ingliston
    Ingliston is a village and district in western Edinburgh, Scotland, best known for hosting the Royal Highland Centre and being adjacent to Edinburgh Airport.
  • D. Etone
    Etone is the historical name for the English town now known as Nuneaton in Warwickshire.
  • E. Helensvale
    Helensvale is a residential suburb and transport hub in the northern part of the Gold Coast in Queensland, Australia.
  • 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_69bd4462ed04819084fcb01eb9d2fa74 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd79f142488190bc6c57b8ff7ef894 completed March 20, 2026, 4:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69bef7f9a1c48190939a5073bd779be6 completed March 21, 2026, 7:56 p.m.
Created at: March 20, 2026, 1:46 p.m.