Triple
T13631472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HSI special agents |
E325727
|
entity |
| Predicate | investigate |
P111372
|
FINISHED |
| Object | human trafficking |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: human trafficking | Statement: [HSI special agents, investigate, human trafficking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: investigate Context triple: [HSI special agents, investigate, human trafficking]
-
A.
investigatedFor
Indicates that an entity is the subject of an investigation concerning a suspected involvement in another entity (typically a crime, incident, or wrongdoing).
-
B.
investigatedUsing
Indicates that an investigation, study, or analysis was carried out by means of a specified method, tool, or resource.
-
C.
helpsInvestigate
Indicates that one entity assists another entity in carrying out an investigation or inquiry.
-
D.
areInvestigatedFor
Indicates that one or more entities are the subject of an investigation concerning a particular issue, incident, or alleged wrongdoing.
-
E.
investigatedBy
Indicates that an entity is the subject of an investigation carried out by another entity.
- F. None of above. chosen
Provenance (4 batches)
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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc60635d08190899806fe8936f02a |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe85e1c4819095194f4b7f9f6118 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc6043e148190a2a25f929cfa35e5 |
completed | April 12, 2026, 4:19 p.m. |
Created at: April 9, 2026, 9:51 p.m.