Triple

T9902281
Position Surface form Disambiguated ID Type / Status
Subject Shardlow wharves E182313 entity
Predicate locatedIn P40 FINISHED
Object Shardlow E81709 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: Shardlow | Statement: [Shardlow wharves, locatedIn, Shardlow]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shardlow
Context triple: [Shardlow wharves, locatedIn, Shardlow]
  • A. Shardlow chosen
    Shardlow is a historic village in Derbyshire, England, known for its canal heritage and role as an important inland port during the industrial era.
  • B. Shillingford
    Shillingford is a small village in South Oxfordshire, England, known for its rural setting near the River Thames and proximity to the town of Benson.
  • C. Minstead
    Minstead is a small village in Hampshire, England, best known as the burial place of Sir Arthur Conan Doyle.
  • D. Windlesham
    Windlesham is a village and civil parish in the Surrey Heath district of Surrey, England, known for its affluent residential character and leafy surroundings.
  • E. Shinfield
    Shinfield is a village and civil parish in Berkshire, England, situated just south of Reading and known for its mix of rural character and expanding residential developments.
  • 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_69ca82876f8081909cf75df0f99bb13f completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cdb4e391888190a3f5e5a1bf1cf9ff completed April 2, 2026, 12:14 a.m.
NED1 Entity disambiguation (via context triple) batch_69d1eb2778bc81909d7e09da718d9afa completed April 5, 2026, 4:55 a.m.
Created at: March 30, 2026, 8:40 p.m.