Triple
T31837133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internal Security and Public Order Department |
E812704
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | division of the Royal Malaysia Police |
C59950
|
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: division of the Royal Malaysia Police Context triple: [Internal Security and Public Order Department, instanceOf, division of the Royal Malaysia Police]
-
A.
branch of the Malaysian Army
A branch of the Malaysian Army is a major organizational subdivision responsible for specific operational functions, capabilities, and support roles within the army’s overall land warfare mission.
-
B.
government agency of Malaysia
A government agency of Malaysia is an official public-sector body established by the Malaysian government to implement policies, deliver services, and regulate specific sectors or functions within the country.
-
C.
division of the New South Wales Police Force
A division of the New South Wales Police Force is an organizational unit responsible for delivering specific policing functions or services within a defined geographic area or operational specialty.
-
D.
division of Sarawak
A division of Sarawak is a primary administrative region within the Malaysian state of Sarawak, serving as a top-level governmental and territorial unit overseeing several districts.
-
E.
district of Malaysia
A district of Malaysia is an administrative subdivision within a state or federal territory, governed by local authorities and serving as a primary unit for local administration, services, and development planning.
- F. None of above. chosen
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_69f348ea7ffc8190a2ab43d80277cf59 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:48 p.m.