Triple
T30657553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | THQ |
E780423
|
entity |
| Predicate | reasonForBankruptcy |
P82149
|
FINISHED |
| Object | poor sales performance |
—
|
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: poor sales performance | Statement: [THQ, reasonForBankruptcy, poor sales performance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForBankruptcy Context triple: [THQ, reasonForBankruptcy, poor sales performance]
-
A.
reasonForBankruptcyFiling
chosen
Indicates the cause, circumstance, or justification that led an entity to file for bankruptcy.
-
B.
companyBankruptcy
Indicates that a company has become insolvent and is undergoing a formal legal process of bankruptcy.
-
C.
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.
-
D.
filedForBankruptcy
Indicates that an entity has formally initiated legal proceedings to declare inability to pay its debts and seek protection or reorganization under bankruptcy law.
-
E.
operatorBankruptcy
Indicates that an operator has entered a state of bankruptcy or formal insolvency proceedings.
- 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_69f224a6d10481909290be1a00fc83b3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: April 29, 2026, 8:30 p.m.