Triple

T15315259
Position Surface form Disambiguated ID Type / Status
Subject TD postcode area E366138 entity
Predicate containsPostTown P2711 FINISHED
Object Peebles E116839 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: Peebles | Statement: [TD postcode area, containsPostTown, Peebles]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Peebles
Context triple: [TD postcode area, containsPostTown, Peebles]
  • A. Peebles chosen
    Peebles is a historic market town in the Scottish Borders, known for its scenic riverside setting, traditional architecture, and outdoor recreation.
  • B. Robertstown
    Robertstown is a small Irish village in County Kildare known for its historic canal-side setting and heritage as a former inland waterways hub.
  • C. Haigslea
    Haigslea is a rural locality in Queensland, Australia, situated within the jurisdiction of the Ipswich City Council.
  • D. Brydekirk
    Brydekirk is a small village in Dumfries and Galloway in southwest Scotland, known for its rural setting and proximity to the River Annan.
  • E. Parkeston
    Parkeston is a village and port area in Essex, England, situated near Harwich and known historically for its railway and maritime connections.
  • 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_69d85a113ee881908e297a1d38dd79fa completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e03dd050108190a584543cb93943a4 completed April 16, 2026, 1:39 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff133d171c8190918c9624bcdb7451 completed May 9, 2026, 10:58 a.m.
Created at: April 10, 2026, 3:16 a.m.