Triple
T670918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House simple resolution |
E12968
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | congressional resolution |
C2561
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: congressional resolution Context triple: [House simple resolution, instanceOf, congressional resolution]
-
A.
United States House resolution
chosen
A United States House resolution is a formal legislative measure introduced and considered solely by the House of Representatives to express opinions, make internal rules, or address matters affecting only the House, without the force of law.
-
B.
Act of Congress
An Act of Congress is a formal law or statute enacted by the United States Congress and, typically upon receiving the President’s signature or a veto override, becomes legally binding federal legislation.
-
C.
revolutionary congress
A revolutionary congress is a formal assembly of representatives convened to lead, coordinate, and legitimize a political or social revolution, often drafting new governing frameworks and strategies for transformative change.
-
D.
United Nations resolution
A United Nations resolution is a formal text adopted by a UN organ that expresses decisions, recommendations, or positions on international issues, guiding member states’ actions and the organization’s activities.
-
E.
constitutional convention
A constitutional convention is a formal gathering of representatives convened to draft, revise, or replace a constitution or fundamental governing framework of a political entity.
- F. None of above.
Provenance (1 batch)
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_69a493355dec819098d4244b2fa34885 |
completed | March 1, 2026, 7:27 p.m. |
Created at: March 1, 2026, 7:36 p.m.