Triple
T10596205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knoxville, Georgia |
E250118
|
entity |
| Predicate | CrawfordCountyCourthouseConstructionYear |
P23965
|
FINISHED |
| Object | 1831 |
—
|
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: 1831 | Statement: [Knoxville, Georgia, CrawfordCountyCourthouseConstructionYear, 1831]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CrawfordCountyCourthouseConstructionYear Context triple: [Knoxville, Georgia, CrawfordCountyCourthouseConstructionYear, 1831]
-
A.
churchConstructionDate
Indicates the date on which a church was constructed or originally built.
-
B.
isOldestCountyIn
Indicates that a county holds the status of being the most ancient or earliest established county within a specified larger region or jurisdiction.
-
C.
garrisonCounty
Indicates that a military garrison is stationed in, or assigned responsibility for, a particular county.
-
D.
existedAsCountyUntil
Indicates that an entity functioned with the status or designation of a county up to a specified end date or time period.
-
E.
constructionDate
chosen
Indicates the date on which an entity (such as a building or structure) was constructed or completed.
- 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.