Triple
T28461101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ejina Banner |
E720156
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | banner-level administrative division |
C15606
|
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: banner-level administrative division Context triple: [Ejina Banner, instanceOf, banner-level administrative division]
-
A.
Second-level administrative division
A second-level administrative division is a territorial unit within a country that is directly below the primary (first-level) administrative regions, such as provinces or states, and typically manages local governance and public services.
-
B.
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.
-
C.
province-level administrative division
A province-level administrative division is a primary subnational territorial unit within a country, governed by its own regional authorities under the framework of the national government.
-
D.
regulatory subdivision
A regulatory subdivision is a defined geographic or administrative area within a jurisdiction established for the purpose of applying, enforcing, or managing specific regulations, policies, or legal requirements.
-
E.
township-level division
chosen
A township-level division is a local administrative unit within a country, typically governing a small urban or rural area below the county level and responsible for basic public services and local governance.
- 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_69f01a58a67c819097936d9e8da8d6e6 |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 2:40 a.m.