Triple
T33790538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annex A: Elimination |
E865919
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regulatory document component |
C54005
|
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: regulatory document component Context triple: [Annex A: Elimination, instanceOf, regulatory document component]
-
A.
regulatory document
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.
-
B.
regulatory agency component
A regulatory agency component is a modular part of a regulatory body responsible for performing specific oversight, rulemaking, enforcement, or compliance functions within a defined domain.
-
C.
Legal instrument component
chosen
A legal instrument component is an individual clause, provision, or structural element that contributes to the meaning, function, or enforceability of a broader legal document or agreement.
-
D.
regulatory provision
A regulatory provision is a specific, authoritative rule or requirement established by a regulatory body to govern conduct, processes, or standards within a defined domain.
-
E.
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.
- 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_69f3498f99f481909cb271f4965a7594 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:45 a.m.