Triple
T8460083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wade–Davis Bill |
E200017
|
entity |
| Predicate | presidentialAction |
P146
|
FINISHED |
| Object | pocket veto |
—
|
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: pocket veto | Statement: [Wade–Davis Bill, presidentialAction, pocket veto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presidentialAction Context triple: [Wade–Davis Bill, presidentialAction, pocket veto]
-
A.
presidentialOrder
chosen
Indicates that an action, decision, or directive is formally issued by a president under their official authority.
-
B.
presidentialDocumentOf
Indicates that a document is officially associated with, produced by, or belonging to a particular presidency or president.
-
C.
authorizesPresident
Indicates that one entity grants the president formal permission or legal power to perform a specific action or set of actions.
-
D.
governmentAction
Indicates actions, decisions, or interventions carried out by a government or its agencies in relation to other entities.
-
E.
governorAction
Indicates that a governor performs, initiates, or is responsible for a specific action or decision.
- 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_69ca83198c4c8190a337bf717d1813f5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe49fca788190a8728ff74f4d26f5 |
completed | March 31, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69cbd0fc634481909842c0a30077bfde |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:10 p.m.