Triple
T7139381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jonathan Wild |
E166401
|
entity |
| Predicate | usedLegalRoleAsCoverFor |
P33645
|
FINISHED |
| Object | criminal activities |
—
|
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: criminal activities | Statement: [Jonathan Wild, usedLegalRoleAsCoverFor, criminal activities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedLegalRoleAsCoverFor Context triple: [Jonathan Wild, usedLegalRoleAsCoverFor, criminal activities]
-
A.
usedCover
Indicates that one entity employed another entity as a protective or concealing cover in a given context.
-
B.
usesCoverOrganizations
chosen
Indicates that an entity operates through or makes use of front or intermediary organizations to conceal its true identity, role, or activities.
-
C.
usedLegalStatus
Indicates that one entity applies or relies on the legal status or classification of another entity in a given context.
-
D.
mayCover
Indicates that one entity is permitted or able to extend over, include, or provide coverage for another entity, either partially or fully.
-
E.
builtOnBehalfOf
Indicates that something was constructed or created by one party acting as a representative or agent for another party.
- F. None of above.
Provenance (3 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_69c6888579d481909e05a8d6b81bf733 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e7759a048190815689298befa8d7 |
completed | March 27, 2026, 8:24 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c932888190b125ca3785b18553 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:45 p.m.