Triple

T20353980
Position Surface form Disambiguated ID Type / Status
Subject Bonville E496092 entity
Predicate nearbyLocality P4647 FINISHED
Object Boambee 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: Boambee | Statement: [Bonville, nearbyLocality, Boambee]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Boambee
Context triple: [Bonville, nearbyLocality, Boambee]
  • A. Boambee chosen
    Boambee is a coastal locality in New South Wales, Australia, situated near the town of Sawtell and known for its residential areas and natural surroundings.
  • B. Boorara
    Boorara is a small locality in Western Australia known historically for its association with gold mining in the Eastern Goldfields region.
  • C. Wallendbeen
    Wallendbeen is a small rural village in New South Wales, Australia, known for its agricultural surroundings and location on key regional transport routes.
  • D. Burarra
    Burarra is an Aboriginal Australian language spoken by the Burarra people of Arnhem Land in the Northern Territory.
  • E. Bunnaloo
    Bunnaloo is a small rural locality in the Riverina region of New South Wales, Australia, known for its agricultural surroundings and close-knit community.
  • 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_69e0b4a3f7f48190b37f354574028ca6 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e67851c7088190ba960a33c6dfa824 completed April 20, 2026, 7:02 p.m.
Created at: April 16, 2026, 11:25 a.m.