Triple

T32427405
Position Surface form Disambiguated ID Type / Status
Subject Richmond County, Georgia E828613 entity
Predicate consolidatedCityCountyWith P174069 FINISHED
Object Augusta, Georgia NE NERFINISHED

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: Augusta, Georgia | Statement: [Richmond County, Georgia, consolidatedCityCountyWith, Augusta, Georgia]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: consolidatedCityCountyWith
Context triple: [Richmond County, Georgia, consolidatedCityCountyWith, Augusta, Georgia]
  • A. hasConsolidatedCityCountySince
    Indicates that a city and county have been formally consolidated into a single unified government entity starting from a specified point in time.
  • B. hasMunicipalConsolidationWith
    Indicates that two or more municipalities have been officially merged or unified into a single administrative entity or structure.
  • C. cityCounty
    Indicates that a city is located within, and administratively belongs to, a specific county.
  • D. isBoroughCoterminousWithCounty
    Indicates that a borough and a county share the exact same geographic boundaries and are effectively the same jurisdictional area.
  • E. includesCounty
    Indicates that a larger geographic or administrative region contains or encompasses a specific county within its boundaries.
  • F. None of above. chosen

Provenance (4 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_69f3491b28bc8190b75cea7a507f337b completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6c2a85d4c81909c399aaecc7c440b completed May 3, 2026, 3:36 a.m.
PD Predicate disambiguation batch_69f6ba6eb32c8190bf405b2011fa48f7 completed May 3, 2026, 3:01 a.m.
PDg Predicate description generation batch_69f6bb344bb48190a8089f29c0063ded completed May 3, 2026, 3:04 a.m.
Created at: May 1, 2026, 12:54 a.m.