Triple
T1702074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TCC |
E36788
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | technical cooperation body |
C7802
|
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: technical cooperation body Context triple: [TCC, instanceOf, technical cooperation body]
-
A.
technical standards body
A technical standards body is an organization that develops, maintains, and promotes agreed-upon technical specifications and protocols to ensure interoperability, safety, and consistency across industries and technologies.
-
B.
WCO body
A WCO body is a standardized, structured representation of data and metadata defined by the World Customs Organization to facilitate consistent, electronic exchange of customs-related information across international systems.
-
C.
international cooperation mechanism
chosen
An international cooperation mechanism is a structured framework, agreement, or institution through which multiple countries coordinate policies, share resources, and jointly address cross-border issues or common goals.
-
D.
technical standard component
A technical standard component is a defined, reusable element or module that conforms to established specifications to ensure compatibility, interoperability, and consistent performance within a larger system or standard.
-
E.
intergovernmental legal body
An intergovernmental legal body is an organization formed by multiple governments to develop, interpret, or oversee the implementation of international legal norms, agreements, and dispute-resolution mechanisms.
- 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_69a886163dec8190859c514232a37a05 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:30 p.m.