Triple
T21634866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Force Bill of 1833 |
E533929
|
entity |
| Predicate | aimedAtEnforcing |
P18859
|
FINISHED |
| Object | federal tariff laws |
—
|
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: federal tariff laws | Statement: [Force Bill of 1833, aimedAtEnforcing, federal tariff laws]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimedAtEnforcing Context triple: [Force Bill of 1833, aimedAtEnforcing, federal tariff laws]
-
A.
enforcement
chosen
Indicates the act of compelling compliance with rules, laws, or agreements through monitoring, pressure, or sanctions.
-
B.
enforcedOn
Indicates that a rule, policy, or constraint is applied with authority to a particular target or subject.
-
C.
aimedToLimit
Indicates an action or policy that was intentionally directed toward restricting, reducing, or constraining something.
-
D.
enforcedLaw
Indicates that an authority actively applies or upholds a specific law to regulate behavior or resolve situations.
-
E.
enablesEnforcementOf
Indicates that one entity provides the authority, means, or conditions necessary for another entity to carry out enforcement actions or apply rules.
- 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_69e0c465ae7481908577b7209fdb2a77 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef538c5fbc8190a3316cf91f9516dc |
completed | April 27, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69e69677b9c48190bf81f795aa8ad74e |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:35 p.m.