Triple
T4695320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Technical Regulations under the 1998 Agreement |
E104127
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | UN regulatory instrument |
C12268
|
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: UN regulatory instrument Context triple: [Global Technical Regulations under the 1998 Agreement, instanceOf, UN regulatory instrument]
-
A.
regulatory authority
A regulatory authority is an official body empowered by law to create, implement, and enforce rules and standards within a specific domain to protect public interests and ensure compliance.
-
B.
regulatory framework
A regulatory framework is a structured set of rules, guidelines, and enforcement mechanisms established by authorities to govern behaviors, processes, and standards within a specific domain.
-
C.
Indian regulation
Indian regulation refers to the body of laws, rules, and guidelines enacted by Indian legislative, executive, and regulatory authorities to govern economic, social, and administrative activities within the country.
-
D.
regulatory document
chosen
A regulatory document is an official written instrument issued by an authority that defines, interprets, or enforces rules, standards, or requirements governing specific activities, entities, or domains.
-
E.
European Union regulation
A European Union regulation is a binding legislative act that applies directly and uniformly in all EU member states without needing national implementing measures, establishing common rules and standards across the Union.
- 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_69bd43df91f481908e9add1b617b60ef |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:17 p.m.