Triple
T32171588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Hoynes |
E821721
|
entity |
| Predicate | resignsFrom |
P173278
|
FINISHED |
| Object | Vice Presidency |
—
|
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: Vice Presidency | Statement: [John Hoynes, resignsFrom, Vice Presidency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resignsFrom Context triple: [John Hoynes, resignsFrom, Vice Presidency]
-
A.
resignsTo
Indicates that one entity formally gives up a position, role, or claim in favor of or directed toward another entity or authority.
-
B.
canResign
Indicates that an entity has the authority or option to voluntarily leave a position, role, or membership.
-
C.
canResignTo
Indicates that one party has the ability or permission to formally resign their position, role, or membership to another designated party or authority.
-
D.
resignationSubmittedBy
Indicates that a resignation has been formally submitted by a specific entity (the submitter) to another party or organization.
-
E.
followedResignationOf
Indicates that one event, state, or action occurred after and as a consequence of a resignation.
- 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_69f3490699a48190bbef96b198e8fade |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6ba75252c8190991e0bb2c6452745 |
completed | May 3, 2026, 3:01 a.m. |
| PD | Predicate disambiguation | batch_69f6b3aa892481908d29283a074e6722 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b42902a081909126c7322858a2b3 |
completed | May 3, 2026, 2:34 a.m. |
Created at: May 1, 2026, 12:33 a.m.