Triple
T9029175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WorldCom, Inc. |
E216124
|
entity |
| Predicate | announcedAccountingIrregularities |
P24219
|
FINISHED |
| Object | June 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: June 2002 | Statement: [WorldCom, Inc., announcedAccountingIrregularities, June 2002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcedAccountingIrregularities Context triple: [WorldCom, Inc., announcedAccountingIrregularities, June 2002]
-
A.
accusationsOfNonComplianceBy
Indicates that one party has formally alleged that another party has failed to meet required rules, standards, or obligations.
-
B.
associatedScandal
Indicates a relationship where an entity is linked to, involved in, or notably connected with a particular scandal.
-
C.
knownIssue
Indicates that the subject has an issue or problem that is already identified, recognized, or documented.
-
D.
fiscalIssue
chosen
Indicates a relationship where an entity is involved in, affected by, or associated with a financial or budgetary problem, concern, or matter.
-
E.
notableEarlyIssue
Indicates that the subject is a significant or noteworthy early edition, release, or version of the object.
- 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_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. |
Created at: March 30, 2026, 7:08 p.m.