Triple
T34675438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Java District |
E890481
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former administrative district of Georgia |
C66145
|
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 administrative district of Georgia Context triple: [Java District, instanceOf, former administrative district of Georgia]
-
A.
county of Georgia
A county of Georgia is a local governmental subdivision of the U.S. state of Georgia, serving as an administrative region for political, legal, and public service functions.
-
B.
protected area of Georgia
A protected area of Georgia is a designated geographic region within the state set aside and managed to conserve its natural, cultural, or recreational resources under specific legal and administrative safeguards.
-
C.
district of Atlanta
A district of Atlanta is a defined geographic subdivision of the city, typically characterized by distinct administrative boundaries, land use patterns, and social, cultural, or economic identities within the broader metropolitan area.
-
D.
former district of Virginia
A former district of Virginia is a previously existing administrative or judicial subdivision within the state of Virginia that has since been reorganized, merged, or dissolved.
-
E.
Abkhaz historical region
An Abkhaz historical region is a geographically defined area traditionally inhabited or governed by Abkhaz people, characterized by its distinct historical, cultural, and political development within the broader Caucasus context.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:05 a.m.