Triple

T12547007
Position Surface form Disambiguated ID Type / Status
Subject East Renfrewshire E299996 entity
Predicate containsSettlement P847 FINISHED
Object Clarkston E843278 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: Clarkston | Statement: [East Renfrewshire, containsSettlement, Clarkston]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Clarkston
Context triple: [East Renfrewshire, containsSettlement, Clarkston]
  • A. Clarkston chosen
    Clarkston is a suburban town in East Renfrewshire, Scotland, forming part of the Greater Glasgow conurbation.
  • B. Summerston
    Summerston is a residential suburb in the north-west of Glasgow, Scotland, known for its housing estates, local amenities, and proximity to open green spaces.
  • C. Kingsville
    Kingsville is a small town in southwestern Ontario, Canada, known for its mild climate, agriculture, and location along the shores of Lake Erie.
  • D. Longview
    Longview is a residential area within the Metropolitan Borough of Knowsley in Merseyside, England.
  • E. Longview
    Longview is a mid-sized city in northeastern Texas known as a regional hub for the oil, gas, and manufacturing industries.
  • 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_69d6ada707008190aaec1238117c9379 completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d95481ba28819099f7cd2de02e8837 completed April 10, 2026, 7:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69f655826bbc8190af20858342c008ff completed May 2, 2026, 7:50 p.m.
Created at: April 8, 2026, 9:57 p.m.