Triple
T6921978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PK-BA |
E160207
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative territorial entity code |
C3353
|
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: administrative territorial entity code Context triple: [PK-BA, instanceOf, administrative territorial entity code]
-
A.
administrative territorial entity
An administrative territorial entity is a geographically defined area governed by an authority that exercises administrative, political, or legal control within its boundaries.
-
B.
administrative code
Administrative code is a structured set of rules and regulations issued by governmental or organizational authorities to guide, control, and standardize administrative actions and procedures.
-
C.
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.
-
D.
geographic code
chosen
A geographic code is a standardized alphanumeric identifier used to represent specific geographic areas or locations for purposes such as mapping, analysis, and data organization.
-
E.
ISO 3166-2 entry
An ISO 3166-2 entry represents a standardized code and associated metadata that uniquely identifies a principal subdivision (such as a state, province, or region) within a specific country defined in ISO 3166-1.
- 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_69c6884d350081908d8a970e4d40ad78 |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:26 p.m.