Triple
T27152028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Carolina Prosecutorial District 32 |
E682415
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | North Carolina prosecutorial district |
C8808
|
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: North Carolina prosecutorial district Context triple: [North Carolina Prosecutorial District 32, instanceOf, North Carolina prosecutorial district]
-
A.
North Carolina House of Representatives district
A North Carolina House of Representatives district is a geographically defined electoral area within the state from which one member is elected to serve in the North Carolina House of Representatives.
-
B.
town in North Carolina
A town in North Carolina is a municipally incorporated community within the state that provides local governance, services, and regulations for its residents under North Carolina law.
-
C.
judicial district
chosen
A judicial district is a defined geographic area within which a particular court or set of courts has legal authority to hear and decide cases.
-
D.
Virginia state court
A Virginia state court is a judicial body within the Commonwealth of Virginia’s unified court system that interprets and applies state law to resolve civil, criminal, family, and administrative disputes arising under its jurisdiction.
-
E.
South Carolina House of Representatives district
A South Carolina House of Representatives district is a geographically defined electoral area within the state of South Carolina that elects one member to serve in the South Carolina House of Representatives.
- 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_69eefaceb2a08190b9659b7f730629f5 |
completed | April 27, 2026, 5:57 a.m. |
Created at: April 27, 2026, 9:14 a.m.