Triple

T11883588
Position Surface form Disambiguated ID Type / Status
Subject Glespin E282717 entity
Predicate locatedIn P40 FINISHED
Object Douglasdale E58327 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: Douglasdale | Statement: [Glespin, locatedIn, Douglasdale]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Douglasdale
Context triple: [Glespin, locatedIn, Douglasdale]
  • A. Douglasdale chosen
    Douglasdale is a historic valley in South Lanarkshire, Scotland, traditionally regarded as the heartland and ancestral territory of Clan Douglas.
  • B. Douglasdale
    Douglasdale is a residential suburb located within the affluent Sandton area of Johannesburg, South Africa.
  • C. Deepdale
    Deepdale is a historic football stadium in Preston, England, best known as the long-time home ground of Preston North End, nicknamed "The Lilywhites."
  • D. Callowhill
    Callowhill is a neighborhood in Philadelphia, Pennsylvania, known for its post-industrial character, loft-style buildings, and proximity to Center City and Northern Liberties.
  • E. Douglasfield
    Douglasfield is a locality in Scotland situated near the Dighty Water stream.
  • 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_69d6ab2a90b08190a4e818821cc93e6d completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8d3a02ad4819090faef0e0be732ee completed April 10, 2026, 10:40 a.m.
NED1 Entity disambiguation (via context triple) batch_69f45854b27c81909304aee5e612f934 completed May 1, 2026, 7:37 a.m.
Created at: April 8, 2026, 9:44 p.m.