Triple
T32247764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Law 116-94 |
E823799
|
entity |
| Predicate | originalBillNumber |
P203453
|
FINISHED |
| Object | H.R. 1865 |
—
|
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. 1865 | Statement: [Public Law 116-94, originalBillNumber, H.R. 1865]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalBillNumber Context triple: [Public Law 116-94, originalBillNumber, H.R. 1865]
-
A.
BOENumber
Indicates a relationship where an entity is associated with a specific BOE (Bill of Entry) identification number used for customs or import documentation.
-
B.
billName
Indicates the official name or title assigned to a specific bill.
-
C.
hasChargeNumber
Indicates that an entity is associated with a specific charge identifier or charge reference number.
-
D.
originalRate
Indicates the initial or base rate associated with something before any changes, adjustments, or discounts are applied.
-
E.
billedThrough
Indicates that one party’s billing or payment is processed via, or routed through, another party or system.
- F. None of above. chosen
Provenance (4 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_69f3490cdda88190a9d61e11252a771f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a01839b071481909f9cc79a6a09387d |
completed | May 11, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_6a017edbed688190baa61cbae5110c8e |
completed | May 11, 2026, 7:01 a.m. |
| PDg | Predicate description generation | batch_6a01839a63a48190a59a6c4464db0eea |
completed | May 11, 2026, 7:22 a.m. |
Created at: May 1, 2026, 12:40 a.m.