Triple
T8552847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Đức Giang |
E202485
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ward-level administrative subdivision |
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: ward-level administrative subdivision Context triple: [Đức Giang, instanceOf, ward-level administrative subdivision]
-
A.
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.
-
B.
subdivision of district
A subdivision of district is an administrative unit that forms a smaller, constituent part of a larger district within a governmental or organizational hierarchy.
-
C.
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.
-
D.
regional administrative branch
A regional administrative branch is a localized division of a larger organization or government responsible for managing operations, implementing policies, and coordinating services within a specific geographic area.
-
E.
commune-level administrative unit
A commune-level administrative unit is the smallest local government division within a country, typically responsible for basic public services, local regulations, and community administration for a town, village, or small group of settlements.
- 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_69ca832610e08190b3b6c6cd2c250255 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:19 p.m.