Triple
T9254658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fairfax County General District Court |
E222410
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Virginia state court |
C25869
|
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: Virginia state court Context triple: [Fairfax County General District Court, instanceOf, Virginia state court]
-
A.
county in Virginia
A county in Virginia is a primary local government and geographic subdivision of the Commonwealth of Virginia, responsible for providing regional services, administration, and governance to the communities within its boundaries.
-
B.
Massachusetts state court
A Massachusetts state court is a judicial body within the Commonwealth of Massachusetts that interprets and applies state law to resolve civil, criminal, and administrative disputes.
-
C.
municipality in Virginia
A municipality in Virginia is a legally incorporated local government entity, such as a city or town, within the Commonwealth of Virginia that provides public services and exercises governmental authority over a defined geographic area.
-
D.
Oregon state court
An Oregon state court is a judicial body within the Oregon state court system that interprets and applies Oregon law to resolve civil, criminal, and administrative disputes arising under state jurisdiction.
-
E.
Virginia congressional district
A Virginia congressional district is a geographically defined area within the Commonwealth of Virginia from which voters elect a single representative to the United States House of Representatives.
- F. None of above. chosen
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_69ca841e4cd481908e738c74e958eaea |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:31 p.m.