Triple
T26043129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Census Bureau New Hampshire jurisdiction |
E647750
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | statistical jurisdiction |
C17269
|
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 jurisdiction Context triple: [United States Census Bureau New Hampshire jurisdiction, instanceOf, statistical jurisdiction]
-
A.
legal jurisdiction
A legal jurisdiction is a defined geographic area or subject-matter domain within which a particular court or governmental authority has the power to create, interpret, and enforce laws.
-
B.
regional jurisdiction
A regional jurisdiction is a defined geographic area within a larger political or administrative system that has specific legal authority, governance responsibilities, and regulatory powers over matters within its boundaries.
-
C.
statistical geographic areas
chosen
Statistical geographic areas are spatially defined regions created for the collection, analysis, and presentation of data about populations, economies, or environments.
-
D.
statistical standard
A statistical standard is an agreed-upon set of rules, definitions, and procedures that ensures consistency, comparability, and reliability in the collection, analysis, and reporting of statistical data.
-
E.
statistical commission
A statistical commission is a formal body, often within a government or international organization, responsible for overseeing the collection, analysis, standardization, and dissemination of statistical data to support informed decision-making and policy 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_69e77e8c88f08190858c4c81bd2e1b9a |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 22, 2026, 9:08 a.m.