Triple
T33328021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presidency of John Tyler |
E853318
|
entity |
| Predicate | vetoedLegislation |
P6515
|
FINISHED |
| Object | bill to re-establish a national bank |
—
|
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: bill to re-establish a national bank | Statement: [Presidency of John Tyler, vetoedLegislation, bill to re-establish a national bank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vetoedLegislation Context triple: [Presidency of John Tyler, vetoedLegislation, bill to re-establish a national bank]
-
A.
vetoedBy
chosen
Indicates that an action, decision, or proposal was rejected or blocked by a specific entity with veto authority.
-
B.
canRejectLegislation
Indicates that an entity has the authority to refuse approval of proposed legislation, thereby preventing it from taking effect.
-
C.
passedLegislation
Indicates that a governing body has formally approved and enacted a specific piece of legislation or law.
-
D.
vetoType
Indicates the specific kind or category of veto applied in a decision-making or approval process.
-
E.
vetoOverridden
Indicates that a previously issued veto has been nullified or reversed by a sufficient overriding authority or vote.
- 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_69f34969614c81909cd99661b0902533 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:34 a.m.