Triple
T1064273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enron accounting scandal |
E22974
|
entity |
| Predicate | peakPublicExposure |
P9692
|
FINISHED |
| Object | late 2001 |
—
|
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: late 2001 | Statement: [Enron accounting scandal, peakPublicExposure, late 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakPublicExposure Context triple: [Enron accounting scandal, peakPublicExposure, late 2001]
-
A.
peakStatus
Indicates the condition or phase of something at its highest or most intense point in its progression or lifecycle.
-
B.
notableExposure
chosen
Indicates that an entity has received significant public attention, visibility, or coverage, making it notably exposed or recognized.
-
C.
exposed
Indicates that one entity has been made visible, revealed, or left unprotected to another entity or to some external influence.
-
D.
publicAccess
Indicates that something is available for use, entry, or viewing by the general public without special restrictions or permissions.
-
E.
madePublicConfessionAt
Indicates that an entity openly admitted or confessed something in a public setting at a specific time or place.
- 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_69a493dada0481909c43649f9843ea91 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8f85cc08190ae03ac6c84936cc5 |
completed | March 1, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69a4b7359eb881909c868a558861cc18 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.