Triple
T32178770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H.R. 748 |
E821926
|
entity |
| Predicate | becameLawOn |
P45102
|
FINISHED |
| Object | 2020-03-27 |
—
|
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: 2020-03-27 | Statement: [H.R. 748, becameLawOn, 2020-03-27]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameLawOn Context triple: [H.R. 748, becameLawOn, 2020-03-27]
-
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.
legislatedOn
Indicates that a legislative body has formally considered, debated, or enacted laws or regulations concerning a particular subject or entity.
-
C.
dateSignedIntoLaw
chosen
Indicates the date on which a law or legal measure was formally approved and enacted into law.
-
D.
wasEnactedAsPartOf
Indicates that one legislative act, rule, or measure was formally established as a component within a larger legislative package, bill, or enactment.
-
E.
lawIntroduced
Indicates that a specific law or piece of legislation has been formally proposed or brought forward for consideration within a legislative or governing 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6ba7bfcd0819099d652fc7db158b8 |
completed | May 3, 2026, 3:01 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:34 a.m.