Triple
T20709629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House Resolution 6 (104th Congress) |
E508998
|
entity |
| Predicate | notRequire |
P6844
|
FINISHED |
| Object | Senate approval |
—
|
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: Senate approval | Statement: [House Resolution 6 (104th Congress), notRequire, Senate approval]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notRequire Context triple: [House Resolution 6 (104th Congress), notRequire, Senate approval]
-
A.
isNotRequiredFor
chosen
Indicates that one entity is not necessary or mandatory for the existence, occurrence, validity, or completion of another entity or process.
-
B.
notEnforcedBy
Indicates that a rule, policy, or obligation is not upheld, imposed, or carried out by the referenced enforcing entity.
-
C.
noticeRequirement
Indicates that one party is obligated to provide advance notification to another party before a specified action, change, or event occurs.
-
D.
nonceRequirement
Indicates that a unique, one-time-use value (nonce) is required to be present or validated as part of the interaction or transaction between entities.
-
E.
notGuaranteed
Indicates that the specified outcome, condition, or obligation is not assured to occur or be fulfilled.
- 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_69e0b4c40ad88190b81f77695366d328 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1961090819090daf7254f90a176 |
completed | April 21, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:14 p.m.