Triple
T34508412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kentucky statistical areas |
E885950
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | statistical region classification |
C45345
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: statistical region classification Context triple: [Kentucky statistical areas, instanceOf, statistical region classification]
-
A.
statistical classification
Statistical classification is the process of assigning items or observations to predefined categories or classes based on their measured features using probabilistic or algorithmic decision rules.
-
B.
statistical classification system
chosen
A statistical classification system is a structured framework that organizes data, entities, or phenomena into predefined categories based on quantitative criteria and statistical methods to enable consistent analysis and comparison.
-
C.
points classification
Points classification is a conceptual class that categorizes entities based on accumulated points or scores according to predefined criteria or performance metrics.
-
D.
statistical region of the Czech Republic
A statistical region of the Czech Republic is a territorial unit defined primarily for the collection, analysis, and presentation of statistical data, often corresponding to NUTS or similar administrative divisions.
-
E.
public land classification
Public land classification is the systematic categorization of government-owned lands based on their designated uses, protections, and management objectives, such as conservation, recreation, resource extraction, or development.
- F. None of above.
Provenance (1 batch)
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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:01 a.m.