Triple
T10920524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack Duquesne |
E257933
|
entity |
| Predicate | suspectedOf |
P21177
|
FINISHED |
| Object | involvement with Sloan Limited |
—
|
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: involvement with Sloan Limited | Statement: [Jack Duquesne, suspectedOf, involvement with Sloan Limited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suspectedOf Context triple: [Jack Duquesne, suspectedOf, involvement with Sloan Limited]
-
A.
isSuspiciousOf
Indicates that one entity believes another entity or situation may be untrustworthy, harmful, or involved in wrongdoing.
-
B.
susceptibleTo
Indicates that one entity is vulnerable or likely to be affected, harmed, or influenced by another entity or factor.
-
C.
suspectedPerpetrator
chosen
Indicates that an entity is believed or alleged to be the person responsible for committing a particular harmful or illegal act.
-
D.
accusedOf
Indicates that one entity has formally alleged or claimed that another entity committed a specific wrongdoing or offense.
-
E.
suspectedSupporter
Indicates that one entity is believed or suspected to support, assist, or be aligned with another entity, but this support is not confirmed.
- 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d77081a0c48190b7aa4a482032d1ea |
completed | April 9, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69d72e799f808190b6ab64fc7586a303 |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:22 p.m.