Triple
T26618238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walter Wade Jr. |
E668123
|
entity |
| Predicate | bribes |
P161054
|
FINISHED |
| Object | legal authorities |
—
|
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: legal authorities | Statement: [Walter Wade Jr., bribes, legal authorities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bribes Context triple: [Walter Wade Jr., bribes, legal authorities]
-
A.
bribedBy
Indicates that an entity has received a bribe from another entity, implying an exchange of value to influence the entity’s actions or decisions.
-
B.
bribeObject
Indicates that something is the item, benefit, or payment offered or given as a bribe in a bribery action.
-
C.
blackmails
Indicates that one entity coerces another by threatening to reveal damaging or sensitive information unless specific demands are met.
-
D.
bounty
Indicates that a reward or payment is offered for performing a specific action or achieving a particular outcome related to an entity.
-
E.
patronage
Indicates a relationship where one party supports, sponsors, or protects another, often in exchange for loyalty, services, or influence.
- 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_69ee9cfe16088190a3dddd68e3c7b1ea |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f615af6b488190819cd865b9b7527e |
completed | May 2, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f60f24ed608190bffe6c6084fc2f7a |
completed | May 2, 2026, 2:50 p.m. |
Created at: April 27, 2026, 2:19 a.m.