Triple
T487034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appomattox Court House, Virginia |
E9900
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former county seat |
C536
|
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: former county seat Context triple: [Appomattox Court House, Virginia, instanceOf, former county seat]
-
A.
former village
A former village is a once-inhabited settlement that has lost its status or population as a village, often due to abandonment, depopulation, or administrative reclassification.
-
B.
former administrative territorial entity
chosen
A former administrative territorial entity is a geographic area that once functioned as an official unit of government or administration but has since been dissolved, merged, or reorganized and no longer holds that status.
-
C.
county in Massachusetts
A county in Massachusetts is an administrative and geographic subdivision of the state that historically provided local government functions, though many have since had their governmental powers reduced or abolished, serving primarily as regional boundaries for courts, law enforcement, and statistical purposes.
-
D.
former political institution
A former political institution is an organization or governing body that once held official political authority or administrative power but has since been dissolved, replaced, or rendered inactive.
-
E.
capital city
A capital city is the municipality designated as the official seat of a country's or region's government, typically hosting its central administrative, legislative, and often judicial institutions.
- 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_69a2e802e2908190ab17c9479e0b6412 |
completed | Feb. 28, 2026, 1:05 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.