Triple
T10596206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knoxville, Georgia |
E250118
|
entity |
| Predicate | servedAsCountySeatFrom |
P26682
|
FINISHED |
| Object | 1823 |
—
|
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: 1823 | Statement: [Knoxville, Georgia, servedAsCountySeatFrom, 1823]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedAsCountySeatFrom Context triple: [Knoxville, Georgia, servedAsCountySeatFrom, 1823]
-
A.
foundedAsCountySeat
Indicates that a place was originally established or designated to serve as the administrative center (county seat) of a county.
-
B.
countySeatSince
chosen
Indicates that one place has served as the official county seat of a county starting from a specified point in time.
-
C.
servedAsStateCapitalFrom
Indicates that one place functioned as the official state capital of a political entity during a specified time period.
-
D.
servedAsStateCapitalUntil
Indicates that a location functioned as the official capital of a state up to a specified end date.
-
E.
usedToBeSeatOf
Indicates that an entity previously served as the official seat or administrative center of another entity, but no longer holds that status.
- 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.