Triple

T16578989
Position Surface form Disambiguated ID Type / Status
Subject Ermine Street E402788 entity
Predicate passesNear P416 FINISHED
Object Royston E220350 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: [Ermine Street, passesNear, Royston]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Royston
Context triple: [Ermine Street, passesNear, Royston]
  • A. Royston chosen
    Royston is a historic market town in Hertfordshire, England, known for the mysterious medieval Royston Cave and its position at the crossroads of ancient routes.
  • B. Royston
    Royston is a small coastal community in British Columbia, Canada, located just south of Courtenay in the Comox Valley on Vancouver Island.
  • C. Royston
    Royston is a masculine given name of English origin, used both as a first name and a surname.
  • D. Royston
    Royston is a residential district in the north of Glasgow, Scotland, known historically for its strong working-class and Irish Catholic community.
  • E. Ruskington
    Ruskington is a large village and civil parish in Lincolnshire, England, known for its rural character and position near the River Slea.
  • 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_69d88387363c8190a97a0c942130de97 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3595f9be88190b01ba628ecf1103d completed April 18, 2026, 10:13 a.m.
NED1 Entity disambiguation (via context triple) batch_6a006eee7e4881908a529717bc449078 completed May 10, 2026, 11:41 a.m.
Created at: April 10, 2026, 5:16 a.m.