Triple
T4893163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office to Monitor and Combat Trafficking in Persons |
E109611
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | anti-human trafficking organization |
C6
|
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: anti-human trafficking organization Context triple: [Office to Monitor and Combat Trafficking in Persons, instanceOf, anti-human trafficking organization]
-
A.
anti-trafficking legislation
Anti-trafficking legislation comprises laws and regulations designed to prevent and punish human trafficking, protect and support victims, and promote cooperation among institutions and jurisdictions to combat trafficking effectively.
-
B.
human trafficking assessment
A human trafficking assessment is a structured evaluation process used to identify potential victims, determine risk factors and exploitation indicators, and guide appropriate protection and intervention measures.
-
C.
nonprofit organization
chosen
A nonprofit organization is an entity formed for purposes other than generating profit, using any surplus revenues to further its mission or public benefit rather than distributing them to owners or shareholders.
-
D.
human rights initiative
A human rights initiative is an organized effort or program aimed at promoting, protecting, and advancing fundamental human rights and freedoms for individuals or communities.
-
E.
activist organization
An activist organization is a coordinated group of individuals who collectively plan and carry out actions to promote, resist, or influence social, political, environmental, or economic change.
- 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_69bd4410bbf88190aad50d2451c863d6 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:28 p.m.