Triple

T14221493
Position Surface form Disambiguated ID Type / Status
Subject Nandewar Range E352505 entity
Predicate locatedNear P294 FINISHED
Object Bingara E909548 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: Bingara | Statement: [Nandewar Range, locatedNear, Bingara]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bingara
Context triple: [Nandewar Range, locatedNear, Bingara]
  • A. Bingara chosen
    Bingara is a small rural town in northern New South Wales, Australia, known for its agricultural surroundings and historic charm along the Gwydir River.
  • B. Chirawa
    Chirawa is a town in the Jhunjhunu district of Rajasthan, India, known for its historic havelis and traditional Rajasthani culture.
  • C. Bolmong
    Bolmong is the commonly used abbreviated name for Bolaang Mongondow Regency, an administrative region in North Sulawesi, Indonesia.
  • D. Gulmit
    Gulmit is a picturesque village in northern Pakistan’s Gilgit-Baltistan region, known for its traditional Wakhi culture, terraced fields, and views of the surrounding Karakoram peaks.
  • E. Lamkang
    Lamkang is a Tibeto-Burman language spoken by the Lamkang people, primarily in parts of Northeast India and Myanmar.
  • 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_69d8278a06e481908b5d6af0a8afe737 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de6213801c8190a47705cd890b9ae7 completed April 14, 2026, 3:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd2813e55881909bdbc6f3c6ef572b completed May 8, 2026, 12:02 a.m.
Created at: April 10, 2026, 1:06 a.m.