Triple
T20803277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enron Creditors Recovery Corp. |
E512092
|
entity |
| Predicate | wasCreatedForBenefitOf |
P1806
|
FINISHED |
| Object | Enron 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: Enron creditors | Statement: [Enron Creditors Recovery Corp., wasCreatedForBenefitOf, Enron creditors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasCreatedForBenefitOf Context triple: [Enron Creditors Recovery Corp., wasCreatedForBenefitOf, Enron creditors]
-
A.
benefice
Indicates that one entity grants or bestows a benefit, favor, or advantage upon another.
-
B.
believedBenefit
Indicates that one entity considers or perceives another entity, action, or state as providing an advantage or positive outcome.
-
C.
benefitsCause
Indicates that one entity gains an advantage, improvement, or positive outcome as a result of another entity or cause.
-
D.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
E.
primaryBeneficiaries
chosen
Indicates which entities are the main recipients or advantaged parties resulting from a particular action, resource, or arrangement.
- 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_69e0b4cc69f481908e98751e697b9df4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2b2d5688190aaa58a2594d4787c |
completed | April 21, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:39 p.m.