Triple
T9029384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WorldCom |
E216129
|
entity |
| Predicate | bankruptcyYear |
P85971
|
FINISHED |
| Object | 2002 |
—
|
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: 2002 | Statement: [WorldCom, bankruptcyYear, 2002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bankruptcyYear Context triple: [WorldCom, bankruptcyYear, 2002]
-
A.
dateOfBankruptcyFiling
Indicates the specific date on which a person or organization formally filed for bankruptcy.
-
B.
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.
-
C.
emergedFromBankruptcy
Indicates that an entity has successfully completed bankruptcy proceedings and returned to normal financial or operational status.
-
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.
bankruptcyCourt
Indicates that a legal matter, case, or proceeding is handled by, filed in, or otherwise associated with a bankruptcy court.
- F. None of above. chosen
Provenance (4 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a9bcb508190b58751f1772407d4 |
completed | April 1, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee132f08190940749c7c522e4c1 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f887108819096d45a186fc137b3 |
completed | March 31, 2026, 11:58 p.m. |
Created at: March 30, 2026, 7:08 p.m.