Triple
T26428129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SwissMaritimeRegulationsOnInlandWaters |
E664422
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nationalRegulation |
C19975
|
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: nationalRegulation Context triple: [SwissMaritimeRegulationsOnInlandWaters, instanceOf, nationalRegulation]
-
A.
regulations
Regulations are authoritative rules or directives established by a governing body to control, manage, or guide behaviors and processes within a specific domain.
-
B.
central government regulations
chosen
Central government regulations are legally binding rules and standards issued by national authorities to direct, control, and coordinate activities within a country in accordance with public policy and law.
-
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.
regional legislation
Regional legislation comprises the laws, regulations, and legal frameworks enacted by subnational authorities (such as states, provinces, or regions) to govern matters within their territorial jurisdiction.
-
E.
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.
- 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_69ee883ad6a4819088f918e76122d690 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 26, 2026, 11:47 p.m.