Triple
T11171875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Keene |
E264291
|
entity |
| Predicate | madeDealWith |
P29943
|
FINISHED |
| Object | federal prosecutors |
—
|
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: federal prosecutors | Statement: [James Keene, madeDealWith, federal prosecutors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: madeDealWith Context triple: [James Keene, madeDealWith, federal prosecutors]
-
A.
hasDealingsIn
Indicates that an entity engages in activities, transactions, or business related to a particular domain, location, or subject.
-
B.
negotiatedAfter
Indicates that one negotiation event occurred later in time than another referenced event or negotiation.
-
C.
soldWith
Indicates that one item is sold together with another item as part of the same transaction or offer.
-
D.
hasNotableDeal
Indicates that an entity is involved in a significant or noteworthy agreement, contract, or transaction with another entity.
-
E.
settlementWith
chosen
Indicates a relationship where one party reaches or maintains a settlement or agreement with another party, typically resolving a dispute or claim.
- 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_69d6aa9dafac8190bd90d2c74f661aa7 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e89660208190b1d9e91529f5d246 |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75cf0e6e88190973694abe2990973 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.