Triple
T5731511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WorldCom accounting scandal |
E126393
|
entity |
| Predicate | positionOfBernardEbbers |
P66142
|
FINISHED |
| Object | Chief Executive Officer of WorldCom |
—
|
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: Chief Executive Officer of WorldCom | Statement: [WorldCom accounting scandal, positionOfBernardEbbers, Chief Executive Officer of WorldCom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOfBernardEbbers Context triple: [WorldCom accounting scandal, positionOfBernardEbbers, Chief Executive Officer of WorldCom]
-
A.
positionOnCrime
Indicates a stance, opinion, or policy position that an entity holds regarding crime or crime-related issues.
-
B.
positionAtSynodOfDort
Indicates the specific stance, role, or viewpoint an entity held during the Synod of Dort.
-
C.
numberOfIndictedPersonsApproximate
Indicates an approximate count of persons who have been formally indicted in a given context or case.
-
D.
positionOnIssue
Indicates the stance or viewpoint an entity holds regarding a specific issue or topic.
-
E.
positionOnPope
Indicates a stance, opinion, or evaluative position that one entity holds regarding the Pope.
- 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_69c0083082288190b7478cead6b5430a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029014588819094a2a0f6f9b66bab |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021c6488881909bed4a4534d57f70 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c028fec2bc819083f5dca6a8d9d435 |
completed | March 22, 2026, 5:38 p.m. |
Created at: March 22, 2026, 3:47 p.m.