Triple
T36849209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Excise Act, 2005 (for import-stage excise) |
E910630
|
entity |
| Predicate | levyOn |
P41654
|
FINISHED |
| Object | specified goods |
—
|
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: specified goods | Statement: [Federal Excise Act, 2005 (for import-stage excise), levyOn, specified goods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: levyOn Context triple: [Federal Excise Act, 2005 (for import-stage excise), levyOn, specified goods]
-
A.
canLevy
chosen
Indicates that an entity has the authority or power to impose and collect a charge, tax, or fine on another entity or resource.
-
B.
levyEndorsement
Indicates that one party formally supports or approves the imposition or collection of a levy, tax, or similar financial charge.
-
C.
levyPopularVote
Indicates that a levy measure is decided or approved through a popular vote of the general electorate.
-
D.
leverage
Indicates using something (such as a resource, asset, or advantage) to exert influence or gain a greater effect or benefit in a situation or relationship.
-
E.
yonMeans
Indicates that one entity serves as the meaning, definition, or semantic content of another entity.
- 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_69f76e8033d48190a59274f86f13be48 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.