Triple
T25930244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Law 111-3 |
E653417
|
entity |
| Predicate | billTypeAtIntroduction |
P21527
|
FINISHED |
| Object | H.R. |
—
|
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: H.R. | Statement: [Public Law 111-3, billTypeAtIntroduction, H.R.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: billTypeAtIntroduction Context triple: [Public Law 111-3, billTypeAtIntroduction, H.R.]
-
A.
billType
chosen
Indicates the classification or category assigned to a bill (such as its kind, purpose, or procedural type).
-
B.
policyIntroduced
Indicates that a specific policy has been formally brought into effect or announced by an authority or organization.
-
C.
billName
Indicates the official name or title assigned to a specific bill.
-
D.
introducedTaxType
Indicates that an entity (such as a government or authority) has brought a particular type of tax into existence or put it into effect.
-
E.
billingAuthorityType
Indicates the specific role or category of authority responsible for issuing or managing a bill in the relationship between the parties.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f60418322081908411c24d1dc820de |
completed | May 2, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 8:36 a.m.