Triple

T15993105
Position Surface form Disambiguated ID Type / Status
Subject Barley E387886 entity
Predicate hasPostTown P2711 FINISHED
Object ROYSTON E742690 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: ROYSTON | Statement: [Barley, hasPostTown, ROYSTON]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ROYSTON
Context triple: [Barley, hasPostTown, ROYSTON]
  • A. ROYSTON chosen
    ROYSTON is a small market town in Hertfordshire, England, known for its historic crossroads location and the mysterious medieval Royston Cave.
  • B. Croston
    Croston is a historic village in Lancashire, England, known for its picturesque rural setting, traditional architecture, and riverside location.
  • C. Ralston
    Ralston is a surname of English and Scottish origin borne by various notable individuals across different fields.
  • D. Rockton
    Rockton is a rural locality in New South Wales, Australia, situated within the Snowy Monaro region.
  • E. 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.
  • 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_69d86daa562c81908aacc179c0fe8fb5 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e15785347081908831b4cbc9a2dd45 completed April 16, 2026, 9:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffc3d3ef2881909213ff608192f1ef completed May 9, 2026, 11:31 p.m.
Created at: April 10, 2026, 4:54 a.m.