Triple
T35904192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Department of Special Investigation (Thailand) |
E1038427
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | specialized investigative body |
C20608
|
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: specialized investigative body Context triple: [Department of Special Investigation (Thailand), instanceOf, specialized investigative body]
-
A.
disciplinary inspection body
A disciplinary inspection body is an organizational unit responsible for monitoring, investigating, and enforcing compliance with rules, ethics, and standards within an institution or system.
-
B.
specialized body of an international organization
A specialized body of an international organization is a distinct, functionally focused entity established within the organization’s framework to carry out specific technical, administrative, or policy-related tasks in support of its overall objectives.
-
C.
specialized arbitration body
A specialized arbitration body is an independent, expert tribunal established to resolve disputes within a particular field or industry through binding or non-binding arbitral decisions.
-
D.
órgano jurídico especializado
Un órgano jurídico especializado es una entidad institucional dotada de competencias técnicas y normativas específicas para interpretar, aplicar o supervisar el cumplimiento del derecho en un ámbito concreto.
-
E.
specialized institution
chosen
A specialized institution is an organization dedicated to a specific field or function, providing focused services, expertise, or education within that domain.
- 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_69f76e2259608190bf6788a132e0d139 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.