Triple

T13764194
Position Surface form Disambiguated ID Type / Status
Subject Habersham County E330693 entity
Predicate containsSettlement P847 FINISHED
Object Clarkesville E1070088 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: Clarkesville | Statement: [Habersham County, containsSettlement, Clarkesville]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Clarkesville
Context triple: [Habersham County, containsSettlement, Clarkesville]
  • A. Clarkesville chosen
    Clarkesville is a small city in northeastern Georgia that serves as the administrative and cultural hub of Habersham County.
  • B. Cedartown
    Cedartown is a small city in northwestern Georgia known historically for its location within the mineral-rich Georgia Gold Belt and its role as a local industrial and railroad hub.
  • C. Loganville
    Loganville is a suburban city in the Atlanta metropolitan area known for its residential communities and small-town character.
  • D. Marshallville
    Marshallville is a small unincorporated community located within Upper Township in Cape May County, New Jersey.
  • E. Saylesville
    Saylesville is a historic mill village located within the town of Lincoln in Providence County, Rhode Island.
  • 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_69d81c583b0081909e408a17db517a21 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de022690ac8190bd5410ecc659a2a7 completed April 14, 2026, 9 a.m.
NED1 Entity disambiguation (via context triple) batch_69fba1b8689c8190b3ef7416000ef89e completed May 6, 2026, 8:16 p.m.
Created at: April 9, 2026, 10:10 p.m.