Triple

T14591908
Position Surface form Disambiguated ID Type / Status
Subject Gympie E342465 entity
Predicate electoralDistrictState P19338 FINISHED
Object Gympie E342465 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: Gympie | Statement: [Gympie, electoralDistrictState, Gympie]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gympie
Context triple: [Gympie, electoralDistrictState, Gympie]
  • A. Gympie chosen
    Gympie is a regional city in Queensland, Australia, historically known for its gold mining heritage and location on the Mary River north of Brisbane.
  • B. Yandina
    Yandina is a town in the Central Province of the Solomon Islands, known as an important local hub for trade and transport in the Russell Islands region.
  • C. Kingaroy
    Kingaroy is a rural town in Queensland, Australia, known as a major peanut-growing center and service hub for the surrounding agricultural region.
  • D. Coorparoo
    Coorparoo is an inner-eastern suburb of Brisbane, Australia, known for its residential character, heritage homes, and proximity to the city centre.
  • E. Tewantin
    Tewantin is a historic riverside town in Queensland, Australia, that serves as one of the main service and residential hubs for the Noosa 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_69d822ddc0f081909cd8163c7de298cd completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb4249af08190962009741d1f7d41 completed April 14, 2026, 9:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69fe9db810c481908dde925ff90f3fa0 completed May 9, 2026, 2:36 a.m.
Created at: April 10, 2026, 1:24 a.m.