Triple

T21183195
Position Surface form Disambiguated ID Type / Status
Subject Illabo railway station E522004 entity
Predicate locatedIn P40 FINISHED
Object Illabo 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: Illabo | Statement: [Illabo railway station, locatedIn, Illabo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Illabo
Context triple: [Illabo railway station, locatedIn, Illabo]
  • A. Illabo chosen
    Illabo is a small rural locality in the Riverina region of New South Wales, Australia, known historically as a farming and railway village.
  • B. Baddega
    Baddega was a prominent monarch of the Vemulavada Chalukya dynasty in early medieval South India, known for his regional power and patronage.
  • C. Illawong
    Illawong is a suburban residential area in southern Sydney, New South Wales, known for its bushland setting between the Georges and Woronora Rivers.
  • D. Boorara
    Boorara is a small locality in Western Australia known historically for its association with gold mining in the Eastern Goldfields region.
  • E. Burarra
    Burarra is an Aboriginal Australian language spoken by the Burarra people of Arnhem Land in the Northern Territory.
  • 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_69e0b50ef1d48190b063aa342667df22 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e7301f7f1c81908686866fdee57127 completed April 21, 2026, 8:06 a.m.
Created at: April 16, 2026, 3:04 p.m.