Triple

T7310940
Position Surface form Disambiguated ID Type / Status
Subject Hume region E168087 entity
Predicate hasTown P847 FINISHED
Object Beechworth E656103 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: Beechworth | Statement: [Hume region, hasTown, Beechworth]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Beechworth
Context triple: [Hume region, hasTown, Beechworth]
  • A. Beechworth chosen
    Beechworth is a historic gold rush-era town in northeastern Victoria, Australia, known for its well-preserved colonial architecture and heritage streetscapes.
  • B. Bairnsdale
    Bairnsdale is a regional town in eastern Victoria, Australia, serving as a key service and transport hub for the surrounding Gippsland area.
  • C. Stawell
    Stawell is a regional town in western Victoria, Australia, known historically for gold mining and as the home of the annual Stawell Gift footrace.
  • D. Warragul
    Warragul is a regional town in Victoria, Australia, serving as a key commercial and service centre for the West Gippsland area.
  • E. Albury
    Albury is a major regional city in New South Wales, Australia, located on the border with Victoria and known as a key commercial and transport hub of the Murray River region.
  • 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_69c6888d8e3c81909db79714903baf31 completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6ebff866081909916796d1b72aee8 completed March 27, 2026, 8:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7fa75d64c8190be20be58c81446e1 completed March 28, 2026, 3:57 p.m.
Created at: March 27, 2026, 3:02 p.m.