Triple
T27959828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ba Commandery |
E704550
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient administrative division |
C32966
|
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: ancient administrative division Context triple: [Ba Commandery, instanceOf, ancient administrative division]
-
A.
ancient district
chosen
An ancient district is a historically defined administrative or geographic area that existed in antiquity, often characterized by distinct political, cultural, or social functions within a larger civilization.
-
B.
former administrative territorial entity
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.
administrative division collection
A collection of administrative divisions is an organized grouping of territorial units (such as states, provinces, or districts) that together represent a structured subdivision of a larger political or geographic entity.
-
D.
former subdivision of a country
A former subdivision of a country is an administrative region or territorial unit that once existed within a nation’s political structure but has since been reorganized, merged, renamed, or abolished.
-
E.
traditional political subdivision
A traditional political subdivision is a historically established territorial unit within a country, such as a province, county, or parish, that serves administrative, legal, and governance functions.
- 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_69ef841061e48190b5570f9562f7434d |
completed | April 27, 2026, 3:43 p.m. |
Created at: April 27, 2026, 7:30 p.m.