Triple
T14084757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Governor-General of Liangguang |
E338962
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | provincial-level administrative post |
C12383
|
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: provincial-level administrative post Context triple: [Governor-General of Liangguang, instanceOf, provincial-level administrative post]
-
A.
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.
-
B.
provincial-level city
A provincial-level city is an urban administrative division that holds the same rank as a province or is directly governed at the provincial level, typically encompassing both a central city and surrounding rural or suburban areas.
-
C.
public administration position
A public administration position is a role within government or public sector organizations responsible for planning, implementing, and managing policies and services that serve the public interest.
-
D.
gubernatorial post
chosen
A gubernatorial post is an official position held by a governor, responsible for leading the executive branch of a state or regional government and implementing laws and policies within that jurisdiction.
-
E.
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.
- 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_69d81c687b0c819087fd9ed4198403f8 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:21 p.m.