Triple
T446412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States v. Lopez |
E7030
|
entity |
| Predicate | definedCategoryOfCommercePower |
P8541
|
FINISHED |
| Object | channels of interstate commerce |
—
|
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: channels of interstate commerce | Statement: [United States v. Lopez, definedCategoryOfCommercePower, channels of interstate commerce]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definedCategoryOfCommercePower Context triple: [United States v. Lopez, definedCategoryOfCommercePower, channels of interstate commerce]
-
A.
energyType
Indicates the kind or category of energy associated with an entity or process.
-
B.
definesPowersOf
chosen
Indicates that one entity specifies or determines the scope, limits, or nature of the authority or powers held by another entity.
-
C.
suppliesPowerTo
Indicates that one entity provides electrical or energy power required for the operation or functioning of another entity.
-
D.
definesPoweringMode
Indicates that one entity specifies or determines the operating or powering mode used by another entity.
-
E.
typeOfUtility
Indicates that one entity is a specific kind or category of utility associated with 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_69a2e7e4676c81909ea0dbdecac0687c |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef62c7a88190851fcd57658b4102 |
completed | Feb. 28, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69a2eddfb5508190a4e06e1b260d8b2b |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.