Triple
T12678554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Incoterms rules |
E302885
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | trade term standard |
C29046
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: trade term standard Context triple: [Incoterms rules, instanceOf, trade term standard]
-
A.
nomenclature for traded products
A standardized system for naming, coding, and categorizing products that are bought and sold in commerce to ensure clear identification, comparison, and communication across markets and stakeholders.
-
B.
technical standard concept
chosen
A technical standard concept is a formally defined specification or guideline that establishes uniform criteria, methods, or requirements to ensure compatibility, safety, quality, and interoperability across technologies, systems, or processes.
-
C.
trade law
Trade law is the body of rules and principles governing the exchange of goods, services, and capital across borders, including treaties, regulations, and dispute resolution mechanisms between nations and commercial entities.
-
D.
commerce clause
The Commerce Clause is a provision in the U.S. Constitution that grants Congress the power to regulate trade and economic activities among the states, with foreign nations, and with Native American tribes.
-
E.
measurement standardization treaty
A measurement standardization treaty is an international agreement that establishes and harmonizes common units, definitions, and procedures for measurements to ensure consistency and comparability across participating countries.
- F. None of above.
Provenance (1 batch)
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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:20 p.m.