Triple

T10596213
Position Surface form Disambiguated ID Type / Status
Subject Knoxville, Georgia E250118 entity
Predicate countySeatStatus P13325 FINISHED
Object historic county seat of Crawford County, Georgia 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: historic county seat of Crawford County, Georgia | Statement: [Knoxville, Georgia, countySeatStatus, historic county seat of Crawford County, Georgia]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: countySeatStatus
Context triple: [Knoxville, Georgia, countySeatStatus, historic county seat of Crawford County, Georgia]
  • A. countySeat
    Indicates that one place serves as the administrative center or capital of a county.
  • B. countySeatFunction chosen
    Indicates that one place serves as the administrative center or seat of government for a county.
  • C. countySeatLocatedAt
    Indicates that a county’s administrative center or capital is located at a specific place or settlement.
  • D. sharesCountySeatStatusWith
    Indicates that two entities have the same status with respect to serving as the county seat (e.g., both are county seats or both are not).
  • E. hasCountySeatCity
    Indicates that a county has a specific city that serves as its official administrative center or county seat.
  • 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_69d381c9d3d48190a29ee491e1696a0e completed April 6, 2026, 9:50 a.m.
NER Named-entity recognition batch_69d5278dacc4819089b759744f100e5f completed April 7, 2026, 3:49 p.m.
PD Predicate disambiguation batch_69d5190a6dfc819088262957551808a1 completed April 7, 2026, 2:47 p.m.
Created at: April 6, 2026, 12:41 p.m.