Triple
T25025923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Badan Usaha Milik Negara |
E626707
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state-owned enterprise in Indonesia |
C7167
|
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: state-owned enterprise in Indonesia Context triple: [Badan Usaha Milik Negara, instanceOf, state-owned enterprise in Indonesia]
-
A.
Indonesian government body
An Indonesian government body is an official public institution established by the state to formulate, implement, and oversee policies, regulations, and services within a specific area of governance in Indonesia.
-
B.
Indonesian government regulation
An Indonesian government regulation is a legally binding rule issued by authorized state institutions to implement, clarify, or operationalize provisions of higher-level laws within Indonesia’s legal system.
-
C.
province of Indonesia
A province of Indonesia is a primary administrative division of the country, each governed by a provincial government headed by a governor and possessing a degree of political and fiscal autonomy under the national framework.
-
D.
government-owned company
chosen
A government-owned company is a legal entity engaged in commercial activities that is wholly or majority owned and controlled by a national, regional, or local government.
-
E.
Malaysian company
A Malaysian company is a legally registered business entity operating in Malaysia, governed by local corporate laws and regulations, and engaged in commercial, industrial, or professional activities.
- 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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 6:07 a.m.