Triple

T33093
Position Surface form Disambiguated ID Type / Status
Subject Commerce Clause E660 entity
Predicate associatedWithDoctrine P1481 FINISHED
Object substantial effects doctrine 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: substantial effects doctrine | Statement: [Commerce Clause, associatedWithDoctrine, substantial effects doctrine]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: associatedWithDoctrine
Context triple: [Commerce Clause, associatedWithDoctrine, substantial effects doctrine]
  • A. teachesDoctrine
    Indicates that one entity imparts, explains, or promotes a specific doctrine or set of beliefs to another entity.
  • B. associatedWithDiscipline
    Indicates that an entity has a relevant connection or involvement with a particular academic, professional, or thematic discipline.
  • C. composer
    Indicates that one entity is the creator or writer of a musical work associated with another entity.
  • D. organizationAssociatedWith
    Indicates that there is a formal or recognized connection or affiliation between an organization and another entity.
  • E. notablyAssociatedWith chosen
    Indicates that one entity is prominently or distinctively connected with another in a way that is especially noteworthy or remarkable.
  • 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_69a2479dec388190967ba648663442c9 completed Feb. 28, 2026, 1:40 a.m.
NER Named-entity recognition batch_69a2496ffc548190b545f998cbebd5b9 completed Feb. 28, 2026, 1:48 a.m.
PD Predicate disambiguation batch_69a248717f5081909952a8c9ed1e1742 completed Feb. 28, 2026, 1:44 a.m.
Created at: Feb. 28, 2026, 1:44 a.m.