Triple
T22753938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benjamin M. Prentiss |
E562782
|
entity |
| Predicate | releasedInPrisonerExchange |
P5178
|
FINISHED |
| Object | 1862 |
—
|
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: 1862 | Statement: [Benjamin M. Prentiss, releasedInPrisonerExchange, 1862]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releasedInPrisonerExchange Context triple: [Benjamin M. Prentiss, releasedInPrisonerExchange, 1862]
-
A.
prisonerExchange
chosen
Indicates a relationship where one party transfers prisoners to another party in return for receiving other prisoners or concessions in exchange.
-
B.
releasedFromInstitutionBy
Indicates that an entity was discharged or set free from an institution through the action or decision of another entity.
-
C.
prisonerOf
Indicates that one entity is held in custody or confinement by another entity, typically under legal or authoritative control.
-
D.
wasRecapturedBy
Indicates that an entity which had previously escaped or been released was caught again by another entity.
-
E.
eventuallyParoled
Indicates that an individual who was previously incarcerated was later released from prison on parole.
- 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_69e24551ec7881909a9c924dbea155f6 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f179bb80ac8190b53a1e00704c4ff5 |
completed | April 29, 2026, 3:23 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:25 p.m.