Triple
T6147722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Law 93-148 |
E137120
|
entity |
| Predicate | houseVetoOverrideVote |
P65343
|
FINISHED |
| Object | 284-135 |
—
|
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: 284-135 | Statement: [Public Law 93-148, houseVetoOverrideVote, 284-135]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: houseVetoOverrideVote Context triple: [Public Law 93-148, houseVetoOverrideVote, 284-135]
-
A.
vetoOverrideBy
Indicates that a decision or law previously vetoed by one authority is subsequently overridden and enacted by another authority with sufficient power.
-
B.
vetoOverridden
Indicates that a previously issued veto has been nullified or reversed by a sufficient overriding authority or vote.
-
C.
vetoOverrideChamber
chosen
Indicates the legislative chamber that has the authority or took action to override a veto.
-
D.
vetoedBy
Indicates that an action, decision, or proposal was rejected or blocked by a specific entity with veto authority.
-
E.
passedHouseVote
Indicates that a proposed measure or bill has received sufficient affirmative votes to be approved by the House of Representatives.
- 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_69c008a2c6308190a56519b22d55d083 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05ce07fb081909278088e9e2e2959 |
completed | March 22, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69c055f39e0881909ae56444b1b48929 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:16 p.m.