Triple

T23044293
Position Surface form Disambiguated ID Type / Status
Subject Albury–Wodonga bypass E573831 entity
Predicate locatedIn P40 FINISHED
Object Wodonga NE NERFINISHED

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: Wodonga | Statement: [Albury–Wodonga bypass, locatedIn, Wodonga]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wodonga
Context triple: [Albury–Wodonga bypass, locatedIn, Wodonga]
  • A. Wodonga chosen
    Wodonga is a regional city in northeastern Victoria, Australia, located on the Victorian side of the Murray River opposite its twin city Albury in New South Wales.
  • B. Ouyen
    Ouyen is a small rural town in northwestern Victoria, Australia, known historically as a service centre for the surrounding Mallee farming region.
  • C. Wooroona
    Wooroona is a rural locality situated within the Banana Shire region of Queensland, Australia.
  • D. Bolwarra
    Bolwarra is a residential suburb in the Maitland region of New South Wales, Australia, known for its semi-rural character and proximity to the Hunter River.
  • E. Moogerah
    Moogerah is a rural locality in Queensland, Australia, known for its scenic landscapes and proximity to Lake Moogerah and the surrounding mountain ranges.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e245b9c11481909d06c872214d21af completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f18517083c8190a0850da5440e0a73 completed April 29, 2026, 4:12 a.m.
Created at: April 17, 2026, 3:54 p.m.