Triple
T1088376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anjou |
E24104
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former county |
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 Context triple: [Anjou, instanceOf, former county]
-
A.
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.
-
B.
county in the United States
A county in the United States is a local administrative and political subdivision of a state (or equivalent), typically responsible for providing regional services such as law enforcement, courts, record-keeping, and infrastructure management for the communities within its boundaries.
-
C.
metropolitan county
A metropolitan county is an administrative region that encompasses a large urban core and its surrounding suburbs, providing coordinated governance and services across the wider metropolitan area.
-
D.
county of Pennsylvania
A county of Pennsylvania is an administrative and geographic subdivision of the Commonwealth of Pennsylvania that provides local government services, maintains public records, and serves as a jurisdictional unit for courts, elections, and taxation.
-
E.
county of California
A county of California is a regional administrative division of the state that provides local government services, governance, and jurisdiction over a defined geographic area and its residents.
- 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_69a49404428c819092dcc9632f5f7b8b |
completed | March 1, 2026, 7:31 p.m. |
Created at: March 1, 2026, 7:42 p.m.