Triple
T26658892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H.R. 1424 |
E666584
|
entity |
| Predicate | wasSignedIntoLawBy |
P60723
|
FINISHED |
| Object | George W. Bush |
—
|
NE NERFINISHED |
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: George W. Bush | Statement: [H.R. 1424, wasSignedIntoLawBy, George W. Bush]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasSignedIntoLawBy Context triple: [H.R. 1424, wasSignedIntoLawBy, George W. Bush]
-
A.
signedIntoLawIn
Indicates that a proposed law or bill was formally approved and enacted by an authorized official in a specific place or jurisdiction.
-
B.
dateSignedIntoLaw
Indicates the date on which a law or legal measure was formally approved and enacted into law.
-
C.
wasEnactedAsPartOf
Indicates that one legislative act, rule, or measure was formally established as a component within a larger legislative package, bill, or enactment.
-
D.
statuteApprovedBy
chosen
Indicates that a statute has received formal approval or authorization from a specified person, body, or authority.
-
E.
ratifiedBy
Indicates that an agreement, treaty, or decision has been formally approved and made officially valid by a specified authority or body.
- 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_69ee9cf8c7188190b9b00270a8a89164 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f616bcf5048190abf0152a1760641c |
completed | May 2, 2026, 3:22 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 2:36 a.m.