Triple
T1453159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tianjin |
E31338
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | municipality directly under the central government of China |
C39
|
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: municipality directly under the central government of China Context triple: [Tianjin, instanceOf, municipality directly under the central government of China]
-
A.
central government
The central government is the primary national authority that exercises overarching political, legislative, and administrative control over a state, coordinating and regulating functions that affect the country as a whole.
-
B.
municipality
chosen
A municipality is a local administrative unit, such as a city, town, or district, governed by elected officials and responsible for providing public services and regulations within its defined geographic area.
-
C.
Special Administrative Region of China
A Special Administrative Region of China is a highly autonomous territorial unit under Chinese sovereignty that maintains its own legal, economic, and administrative systems distinct from those of mainland China.
-
D.
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.
-
E.
municipal government position
A municipal government position is a role within a city or local government responsible for administering public services, implementing local policies, and managing community resources and regulations.
- 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_69a499171a28819085b993a3ac78e363 |
completed | March 1, 2026, 7:52 p.m. |
Created at: March 1, 2026, 8 p.m.