Triple
T29822259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H.R.3261 |
E757273
|
entity |
| Predicate | hasCommitteeReferral |
P121536
|
FINISHED |
| Object | House Judiciary Committee |
—
|
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: House Judiciary Committee | Statement: [H.R.3261, hasCommitteeReferral, House Judiciary Committee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommitteeReferral Context triple: [H.R.3261, hasCommitteeReferral, House Judiciary Committee]
-
A.
hasCommittee
Indicates that an entity is associated with or overseen by a specific committee.
-
B.
committeeReferral
chosen
Indicates that a matter (such as a bill, proposal, or issue) has been formally assigned or directed to a specific committee for consideration or action.
-
C.
hasCommitteeName
Indicates that an entity (such as a committee) is associated with a specific official name.
-
D.
assignedByCommittee
Indicates that an assignment or decision was made by a committee rather than by an individual.
-
E.
hasCommitteeType
Indicates that an entity is associated with a committee of a specified type or classification.
- 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_69f2245701c88190ad42415a0956c4ed |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a00acf86e4081909aad9356650e0f79 |
completed | May 10, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_6a00ac813fd08190a0a7782609e74e70 |
completed | May 10, 2026, 4:04 p.m. |
Created at: April 29, 2026, 5:29 p.m.