Triple
T21214455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appalachian state governments |
E522799
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | group of subnational governments |
C38796
|
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: group of subnational governments Context triple: [Appalachian state governments, instanceOf, group of subnational governments]
-
A.
group of national governments
A group of national governments is a collective of sovereign state authorities that coordinate policies, decisions, or actions on shared interests or issues.
-
B.
group of local government areas
chosen
A group of local government areas is a collection of neighboring administrative regions that are organized together for coordinated governance, planning, and service delivery.
-
C.
sub‑national government
A sub-national government is a governing authority below the national level—such as a state, province, region, or municipality—that exercises political, administrative, and often fiscal powers within a defined territorial jurisdiction.
-
D.
group of government ministries
A group of government ministries is a coordinated collection of specialized administrative departments, each responsible for a particular policy area, that together implement and manage a government's public functions and services.
-
E.
subnational foreign affairs body
A subnational foreign affairs body is a governmental entity below the national level (such as a state, province, or city office) that manages international relations, cooperation, and representation on behalf of its jurisdiction.
- 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_69e0b511ed84819099b449b4a111085c |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 3:39 p.m.