Triple
T18806729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theranos |
E459893
|
entity |
| Predicate | liquidation |
P45397
|
FINISHED |
| Object | assets distributed to creditors |
—
|
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: assets distributed to creditors | Statement: [Theranos, liquidation, assets distributed to creditors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liquidation Context triple: [Theranos, liquidation, assets distributed to creditors]
-
A.
liquidationBegan
chosen
Indicates that the process of winding up and dissolving an entity, typically by selling its assets to pay creditors, has started.
-
B.
liquidationDate
Indicates the date on which an entity is formally wound up, dissolved, or its assets are converted to cash in a liquidation process.
-
C.
purposeOfLiquidation
Indicates that a liquidation event is carried out for a specific intended purpose or objective.
-
D.
bankruptcy
Indicates a legal and financial state in which an entity is unable to meet its debt obligations and enters a formal process to resolve or discharge those debts.
-
E.
liabilitiesAtBankruptcy
Indicates the total obligations or debts an entity has outstanding at the time it is declared bankrupt.
- 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a3d7f8d08190a3e02fab6dc40bb5 |
completed | April 20, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69e48d1b10ec8190985c6fb5766ff981 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.