Triple
T35927924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FTX |
E1039074
|
entity |
| Predicate | allegedMisuseOf |
P49815
|
FINISHED |
| Object | customer deposits |
—
|
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: customer deposits | Statement: [FTX, allegedMisuseOf, customer deposits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedMisuseOf Context triple: [FTX, allegedMisuseOf, customer deposits]
-
A.
allegedUse
chosen
Indicates that something is claimed or suspected to have been used, without confirming that the use actually occurred.
-
B.
misuseCanConstitute
Indicates that improper or incorrect use of something can amount to, or be considered as, a particular offense, violation, or condition.
-
C.
riskIfMisused
Indicates that the subject has the potential to cause harm, danger, or negative consequences if it is used improperly or irresponsibly.
-
D.
isOftenMisusedBy
Indicates that something is frequently used incorrectly or inappropriately by a particular entity or group.
-
E.
allegedAction
Indicates that an action is claimed or asserted to have occurred, typically without being proven or 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_69f76e23e4688190a5369138755138bf |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:07 p.m.