Triple

T10855083
Position Surface form Disambiguated ID Type / Status
Subject Bunbury Airport E256247 entity
Predicate serves P98 FINISHED
Object Bunbury E51812 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: Bunbury | Statement: [Bunbury Airport, serves, Bunbury]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bunbury
Context triple: [Bunbury Airport, serves, Bunbury]
  • A. Bunbury chosen
    Bunbury is a coastal city in Western Australia known as a regional port and commercial hub south of Perth.
  • B. Wooster
    Wooster is a small city in northeastern Ohio known for hosting the College of Wooster and serving as the seat of Wayne County.
  • C. Hotton
    Hotton is a small Belgian town in the Ardennes region, known for its scenic riverside setting, caves, and outdoor recreation along the Ourthe River.
  • D. Farnum
    Farnum is a locality within Providence County, Rhode Island, likely a small village or neighborhood rather than an incorporated city.
  • E. Broadford
    Broadford is a village on the Isle of Skye in Scotland’s Inner Hebrides, known as one of the island’s main population centers and a base for exploring the surrounding landscapes.
  • 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_69d6aa83d1448190a66d93c32394d21f completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d75135df24819090ce43afa3ea9b38 completed April 9, 2026, 7:11 a.m.
NED1 Entity disambiguation (via context triple) batch_69e154c05bf081909d1892c6c81a5f2c completed April 16, 2026, 9:29 p.m.
Created at: April 8, 2026, 9:20 p.m.