Triple
T34280678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ex parte Garland |
E879580
|
entity |
| Predicate | pardonRecipient |
P52361
|
FINISHED |
| Object | Augustus Hill Garland |
—
|
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: Augustus Hill Garland | Statement: [Ex parte Garland, pardonRecipient, Augustus Hill Garland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pardonRecipient Context triple: [Ex parte Garland, pardonRecipient, Augustus Hill Garland]
-
A.
pardonReceivedFrom
Indicates that one entity has been officially forgiven or had penalties removed by another authority or individual.
-
B.
recipientOf
chosen
Indicates that one entity is the receiver or beneficiary of something (such as an item, message, or action) from another entity.
-
C.
primaryRecipient
Indicates the entity that is the main or principal receiver of something, such as a message, resource, or benefit, in a given context.
-
D.
pardonOrRelease
Indicates that an authority formally forgives an entity for an offense or frees them from custody, penalty, or imposed restrictions.
-
E.
grantRecipient
Indicates that one entity is the recipient or beneficiary of a grant provided by another entity.
- 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_69f349b5f6648190b9420d94a4cd16e0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:57 a.m.