Triple

T35549896
Position Surface form Disambiguated ID Type / Status
Subject United States–Mexico–Canada Agreement region (US) E1027325 entity
Predicate automotiveRulesOfOriginParty P183235 FINISHED
Object yes 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: yes | Statement: [United States–Mexico–Canada Agreement region (US), automotiveRulesOfOriginParty, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: automotiveRulesOfOriginParty
Context triple: [United States–Mexico–Canada Agreement region (US), automotiveRulesOfOriginParty, yes]
  • A. participatingParty
    Indicates that an entity is involved as a participant in a particular event, activity, or transaction.
  • B. arePartyTo
    Indicates that the entities are participants or signatories in the same agreement, contract, or legal arrangement.
  • C. customsRegime
    Indicates the specific customs treatment or regulatory framework under which goods are imported, exported, or stored.
  • D. legalStatusOfTariffProvisions
    Indicates the legal validity, enforceability, or standing of specific tariff provisions within a regulatory or contractual framework.
  • E. cargoOrigin
    Indicates that a specified location is the starting point from which the cargo was initially shipped or dispatched.
  • F. None of above. chosen

Provenance (4 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_69f76e014fd481909e9f04ac603a2aa9 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f79a54aa3c8190b2bb5d790b2d42d4 completed May 3, 2026, 6:56 p.m.
PD Predicate disambiguation batch_69f7961970408190b669cc556e30a608 completed May 3, 2026, 6:38 p.m.
PDg Predicate description generation batch_69f79a53ccc481908421ae16e69aa8a4 completed May 3, 2026, 6:56 p.m.
Created at: May 3, 2026, 4:04 p.m.