Triple

T9874329
Position Surface form Disambiguated ID Type / Status
Subject Burley Park railway station E240035 entity
Predicate serves P98 FINISHED
Object Burley E826666 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: Burley | Statement: [Burley Park railway station, serves, Burley]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Burley
Context triple: [Burley Park railway station, serves, Burley]
  • A. Burley chosen
    Burley is a suburban area of Leeds in West Yorkshire, England, known for its residential neighborhoods and proximity to the city center.
  • B. Burley
    Burley is a small agricultural and commercial city in south-central Idaho known for its farming, food processing, and location along the Snake River.
  • C. Fernley
    Fernley is a small city in western Nevada known for its location along Interstate 80 and its role as a growing residential and logistics hub near Reno.
  • D. Riverton
    Riverton is a suburban city in the southern part of the Salt Lake Valley in Utah, known for its residential communities and family-oriented amenities.
  • E. Burley, Idaho
    Burley, Idaho is a small city in south-central Idaho that serves as a regional agricultural and commercial hub along the Snake River.
  • 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_69ca84e8a0788190b9061811d50fd554 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdb3f89fa081908b58956902c193cf completed April 2, 2026, 12:10 a.m.
NED1 Entity disambiguation (via context triple) batch_69d1eae5a31c81908085f637fbbff6d2 completed April 5, 2026, 4:53 a.m.
Created at: March 30, 2026, 8:37 p.m.