Triple

T12978109
Position Surface form Disambiguated ID Type / Status
Subject Glenn County E321581 entity
Predicate hasCommunity P2605 FINISHED
Object Stonyford E535282 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: Stonyford | Statement: [Glenn County, hasCommunity, Stonyford]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Stonyford
Context triple: [Glenn County, hasCommunity, Stonyford]
  • A. Stonyford chosen
    Stonyford is a small rural community in Northern California known for its proximity to the Mendocino National Forest and outdoor recreation opportunities.
  • B. Sharneyford
    Sharneyford is a small settlement in Lancashire, England, situated within the Rossendale Valley near the border with West Yorkshire.
  • C. Durford
    Durford is a small settlement in West Sussex, England, situated in the countryside near the River Rother.
  • D. Stakeford
    Stakeford is a village in Northumberland, England, situated near the River Wansbeck and forming part of the wider Wansbeck area.
  • E. Battisford
    Battisford is a small rural village and civil parish located in the English county of Suffolk.
  • 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_69d80763bd6c819094437da5b20b01d2 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69d97e59a4c88190907d05b8d57dae89 completed April 10, 2026, 10:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6b8f0315c8190aae5908ba65d5867 completed May 3, 2026, 2:54 a.m.
Created at: April 9, 2026, 8:38 p.m.