Triple
T13961034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Statutory Pay-As-You-Go Act of 2010 |
E335790
|
entity |
| Predicate | penaltyMechanism |
P112422
|
FINISHED |
| Object | sequestration |
—
|
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: sequestration | Statement: [Statutory Pay-As-You-Go Act of 2010, penaltyMechanism, sequestration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: penaltyMechanism Context triple: [Statutory Pay-As-You-Go Act of 2010, penaltyMechanism, sequestration]
-
A.
penaltyRules
Indicates the rules or conditions under which penalties are defined, applied, or enforced in a given context.
-
B.
movementPenaltyMechanic
Indicates a game or system mechanic that imposes a penalty or disadvantage on an entity’s movement under certain conditions.
-
C.
penaltyProvision
Indicates that a rule, contract, or law includes a clause specifying a punishment or sanction for non-compliance or violation.
-
D.
defaultPenalty
Indicates that a standard or automatically applied penalty is imposed in the absence of a specific or overridden penalty.
-
E.
supportsPenalty
Indicates that one entity endorses, approves of, or is in favor of a particular penalty being applied to another entity or situation.
- 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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e7b2f908190aa32f22298964746 |
completed | April 14, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69de05a3ccf88190b45c742db483fa08 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239524688190a0f2408c239cfcaa |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:17 p.m.