Triple
T35301809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regent of Minahasa |
E1019525
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local executive position |
C10049
|
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: local executive position Context triple: [Regent of Minahasa, instanceOf, local executive position]
-
A.
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.
-
B.
executive position
An executive position is a high-level organizational role responsible for setting strategic direction, making major decisions, and overseeing the performance and operations of a company or its key divisions.
-
C.
county government position
chosen
A county government position is a public office or role within a county’s administrative structure responsible for delivering local services, enforcing county policies, and representing the interests of county residents.
-
D.
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.
-
E.
executive office-holder
An executive office-holder is an individual who occupies a formal position of authority within an organization or government, empowered to make and implement decisions, manage operations, and represent the entity in official capacities.
- 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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.