Triple
T21063782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edwin Edwards |
E518914
|
entity |
| Predicate | chargeRelatedTo |
P41872
|
FINISHED |
| Object | manipulation of riverboat casino licenses |
—
|
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: manipulation of riverboat casino licenses | Statement: [Edwin Edwards, chargeRelatedTo, manipulation of riverboat casino licenses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chargeRelatedTo Context triple: [Edwin Edwards, chargeRelatedTo, manipulation of riverboat casino licenses]
-
A.
charge
Indicates that one entity formally accuses another of an offense or imposes a financial cost or obligation on them.
-
B.
chargesWere
Indicates that specific accusations or legal charges existed or were formally brought against an entity at some point in time.
-
C.
chargeOnChief
Indicates that a formal accusation or legal charge is filed against a chief or primary authority figure.
-
D.
chargesVia
Indicates that one entity charges or powers another entity using a specified medium, method, or interface.
-
E.
associatedWithCharge
chosen
Indicates a relationship where an entity is linked to, involved in, or connected with a specific charge or accusation.
- 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_69e0b505ef108190b25dd4033e2ff7eb |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6feb29e388190a80fa969a4daa606 |
completed | April 21, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf9d71881908cd85dfc37db93ca |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:42 p.m.