Triple
T23152670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Law of 23 June 1972 on the national flag |
E578360
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Luxembourg law |
C47303
|
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: Luxembourg law Context triple: [Law of 23 June 1972 on the national flag, instanceOf, Luxembourg law]
-
A.
Belgian federal law
Belgian federal law is the body of legal rules and principles enacted or recognized by the federal institutions of Belgium that apply uniformly across the entire country on matters within federal competence, such as justice, defense, social security, and monetary policy.
-
B.
Swiss federal law
Swiss federal law is the body of legal rules and principles enacted or recognized at the national level in Switzerland that uniformly govern matters within the competence of the Swiss Confederation across all cantons.
-
C.
Lebanese law
Lebanese law is the hybrid legal system governing Lebanon, combining civil law principles, Ottoman and French legal legacies, and religious personal status laws applied by various sectarian courts.
-
D.
Hungarian law
Hungarian law is the legal system of Hungary, based on a civil law tradition that combines codified statutes, constitutional principles, and European Union legal norms to regulate public, private, and criminal matters within the country.
-
E.
government body of Luxembourg
A government body of Luxembourg is an official public institution or authority responsible for exercising legislative, executive, or judicial functions, or providing administrative services within the Grand Duchy of Luxembourg.
- F. None of above. chosen
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_69e245fb8de081908f0eba7b5fd75bc4 |
completed | April 17, 2026, 2:38 p.m. |
Created at: April 17, 2026, 4:01 p.m.