Triple
T6177813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Committee on Printing |
E137862
|
entity |
| Predicate | isBicameralJointCommittee |
P69505
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Joint Committee on Printing, isBicameralJointCommittee, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBicameralJointCommittee Context triple: [Joint Committee on Printing, isBicameralJointCommittee, true]
-
A.
hasBicameralStructure
Indicates that an entity possesses a two-chamber (two-house) internal organizational or legislative structure.
-
B.
isUnicameral
Indicates that a legislative body consists of a single chamber or house, rather than multiple separate chambers.
-
C.
hasCommittee
Indicates that an entity is associated with or overseen by a specific committee.
-
D.
isBicameralPartnerOf
Indicates that one legislative body or chamber forms one of the two cooperating parts of a bicameral partnership with another.
-
E.
isBipartisan
Indicates that an action, decision, or stance is supported or undertaken by members of two (or more) opposing political parties.
- 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_69c008a80f748190ba3d07ffc81acb29 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05dc9f3d88190ab46b3b246f5a8df |
completed | March 22, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c055fa0a808190bda37832e3ac150c |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056c87340819088003f427706ebf8 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:18 p.m.