Triple
T28580626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2009 NFC Championship |
E723363
|
entity |
| Predicate | relatedScandal |
P29490
|
FINISHED |
| Object | New Orleans Saints bounty scandal |
—
|
NE NERFINISHED |
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: New Orleans Saints bounty scandal | Statement: [2009 NFC Championship, relatedScandal, New Orleans Saints bounty scandal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedScandal Context triple: [2009 NFC Championship, relatedScandal, New Orleans Saints bounty scandal]
-
A.
associatedScandal
chosen
Indicates a relationship where an entity is linked to, involved in, or notably connected with a particular scandal.
-
B.
effectOfScandal
Indicates the consequences or impact that a particular scandal has on a person, organization, event, or situation.
-
C.
legalStatusAfterScandal
Indicates the legal condition or standing an entity has as a result of, or following, a scandal.
-
D.
timeOfMajorScandal
Indicates the specific time period during which a major scandal involving the entity occurred.
-
E.
rescuedFromScandalBy
Indicates that one party’s reputation or situation was saved or rehabilitated from a scandal through the actions or intervention of another party.
- 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_69f01d7e97708190ae9e77ee66a68abd |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a002dd4066c8190945a09ed82f44f3f |
completed | May 10, 2026, 7:03 a.m. |
| PD | Predicate disambiguation | batch_6a002b141f4081909999e14988105f3a |
completed | May 10, 2026, 6:52 a.m. |
Created at: April 28, 2026, 4:14 a.m.