Triple
T126089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Civil Rights Act of 1866 |
E2553
|
entity |
| Predicate | vetoStatus |
P127
|
FINISHED |
| Object | vetoed and overridden |
—
|
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: vetoed and overridden | Statement: [Civil Rights Act of 1866, vetoStatus, vetoed and overridden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vetoStatus Context triple: [Civil Rights Act of 1866, vetoStatus, vetoed and overridden]
-
A.
electoralStatus
Indicates the current state or condition of an entity in relation to an election process (e.g., running, elected, defeated, or not a candidate).
-
B.
status
chosen
Indicates the current condition, state, or standing of an entity within a given context.
-
C.
hasVoteSplit
Indicates that a collective decision or vote resulted in differing choices among participants rather than unanimous agreement.
-
D.
vetoOverrideRequirement
Indicates the conditions or threshold (such as a required majority) needed for a legislative body to override an executive veto.
-
E.
voteCountedIn
Indicates that a particular vote has been included in the official tally for a specific election, contest, or jurisdiction.
- 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_69a251b54ea88190b18281669f59b4c0 |
completed | Feb. 28, 2026, 2:23 a.m. |
| NER | Named-entity recognition | batch_69a25760af348190bf402089c240887d |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a2564c11208190ad25495609d94d87 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:27 a.m.