Triple
T780459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elliot Richardson |
E16483
|
entity |
| Predicate | refusedTo |
P438
|
FINISHED |
| Object | dismiss special prosecutor Archibald Cox |
—
|
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: dismiss special prosecutor Archibald Cox | Statement: [Elliot Richardson, refusedTo, dismiss special prosecutor Archibald Cox]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refusedTo Context triple: [Elliot Richardson, refusedTo, dismiss special prosecutor Archibald Cox]
-
A.
rejectedBy
chosen
Indicates that one entity has been refused, dismissed, or not accepted by another entity.
-
B.
rejectedOrModifiedBy
Indicates that a proposal, request, or item was either not accepted as-is or was altered by a particular agent or authority.
-
C.
rejectedClaim
Indicates that one party has refused to accept, approve, or validate a claim made by another party.
-
D.
cannot
Indicates that one entity lacks the ability, permission, or possibility to perform an action or participate in a specified relationship with another entity.
-
E.
declinedDuring
Indicates that one entity’s value, condition, or status decreased over the course of a specified time period or event.
- 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_69a4936ad1fc81908f190208059ccf78 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a90365648190ace53b0f0e87aa68 |
completed | March 1, 2026, 9 p.m. |
| PD | Predicate disambiguation | batch_69a4a50bd23081908908235b8ec9201e |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.