Triple

T19885135
Position Surface form Disambiguated ID Type / Status
Subject Cusseta, Georgia E477877 entity
Predicate hasCountySeatRoleSince P26682 FINISHED
Object creation of Chattahoochee County LITERAL 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: creation of Chattahoochee County | Statement: [Cusseta, Georgia, hasCountySeatRoleSince, creation of Chattahoochee County]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCountySeatRoleSince
Context triple: [Cusseta, Georgia, hasCountySeatRoleSince, creation of Chattahoochee County]
  • A. countySeatSince chosen
    Indicates that one place has served as the official county seat of a county starting from a specified point in time.
  • B. hasCountySeatWithRole
    Indicates that a county has a designated county seat that fulfills a specific administrative or governmental role.
  • C. hasCountySeatCity
    Indicates that a county has a specific city that serves as its official administrative center or county seat.
  • D. hasCountySeatOn
    Indicates that a county’s administrative center (county seat) is located on or adjacent to a specified geographic feature or infrastructure.
  • E. hasCountySeatOf
    Indicates that a place serves as the administrative county seat (capital) of a specified county.
  • F. None of above.

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_69d8e51f32b08190b3687f4f60353250 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e659093df081909d3be9c3caeb79ba completed April 20, 2026, 4:49 p.m.
PD Predicate disambiguation batch_69e537e8c4e481909fe95d795b4864e7 completed April 19, 2026, 8:15 p.m.
Created at: April 10, 2026, 1:52 p.m.