Triple

T10277579
Position Surface form Disambiguated ID Type / Status
Subject Harling Road E241007 entity
Predicate nearbySettlement P350 FINISHED
Object Larling E637615 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: Larling | Statement: [Harling Road, nearbySettlement, Larling]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Larling
Context triple: [Harling Road, nearbySettlement, Larling]
  • A. Larling chosen
    Larling is a small village in Norfolk, England, situated in a rural area of the Breckland district.
  • B. Glenboig
    Glenboig is a village in North Lanarkshire, Scotland, historically known for its fireclay and brickmaking industry.
  • C. Briggswath
    Briggswath is a small village in North Yorkshire, England, situated near the River Esk and close to the coastal town of Whitby.
  • D. Laurieston
    Laurieston is a district in Glasgow, Scotland, known for its central location near the River Clyde and mix of residential and urban redevelopment areas.
  • E. Cowlairs
    Cowlairs is an area in the north of Glasgow, Scotland, historically known for its railway engineering and industrial facilities.
  • 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_69d381a94c1881908fc38fc263d9b9c2 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4d29f0cf08190a2c5e7523d5c731e completed April 7, 2026, 9:47 a.m.
NED1 Entity disambiguation (via context triple) batch_69d7fb440b9c81909db46299053e11da completed April 9, 2026, 7:17 p.m.
Created at: April 6, 2026, 11:37 a.m.