Triple
T33504473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presidential Proclamation 7219 |
E858076
|
entity |
| Predicate | enforcementPurpose |
P128618
|
FINISHED |
| Object | customs 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: customs laws | Statement: [Presidential Proclamation 7219, enforcementPurpose, customs laws]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enforcementPurpose Context triple: [Presidential Proclamation 7219, enforcementPurpose, customs laws]
-
A.
enforcement
Indicates the act of compelling compliance with rules, laws, or agreements through monitoring, pressure, or sanctions.
-
B.
purposeOfLaw
chosen
Indicates that a law exists or is designed for a particular goal, function, or intended effect.
-
C.
legalCodePurpose
Indicates that a legal code or statute exists for the purpose of achieving, regulating, or addressing a particular goal, issue, or function.
-
D.
entryPurpose
Indicates the reason or intended use for which an entity is being entered, accessed, or recorded in a given context.
-
E.
governedForPurpose
Indicates that one entity exercises governance or control over another specifically to achieve a particular purpose or intended function.
- 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_69f3497660508190a541826a81f7e9ab |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e59dcc40819098acbe7224febc83 |
completed | May 3, 2026, 6:05 a.m. |
| PD | Predicate disambiguation | batch_69f6e3db74c081909a991309d835d477 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:38 a.m.