Triple
T16405460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malaysia Airports Holdings Berhad |
E398413
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state-linked company |
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-linked company Context triple: [Malaysia Airports Holdings Berhad, instanceOf, state-linked company]
-
A.
associated state
An associated state is a political entity that maintains internal self-governance while delegating certain sovereign powers, such as defense or foreign affairs, to a larger, partner state under a formal agreement.
-
B.
associated state
An associated state is a political entity that maintains internal self-government while delegating certain sovereign powers, such as defense or foreign affairs, to a larger, partner state under a formal association agreement.
-
C.
state-like entity
A state-like entity is an abstraction that encapsulates a distinct configuration of conditions or behaviors within a system, often determining how the system responds to inputs at a given time.
-
D.
tribally owned holding company
A tribally owned holding company is a business entity owned and controlled by a Native American tribe or tribal government that manages and oversees a portfolio of subsidiary enterprises to generate revenue, support economic development, and advance tribal sovereignty and community goals.
-
E.
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.
- 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:09 a.m.