Triple
T28169806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artikel 43 Grondwet |
E715424
|
entity |
| Predicate | rechtskarakter |
P13138
|
FINISHED |
| Object | dwingend recht |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: dwingend recht | Statement: [Artikel 43 Grondwet, rechtskarakter, dwingend recht]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rechtskarakter Context triple: [Artikel 43 Grondwet, rechtskarakter, dwingend recht]
-
A.
rechtskracht
Indicates that a legal decision, rule, or act has binding legal force and is formally effective and enforceable.
-
B.
characterizesRightsAs
Indicates that one entity describes, defines, or portrays the nature or status of another entity’s rights in a particular way.
-
C.
gehörtZuRechtsgebiet
Indicates that something is assigned or belongs to a particular legal field or area of law.
-
D.
karakter
Indicates that one entity is a character (e.g., a role or persona) associated with or embodied by another entity.
-
E.
legalCharacterization
chosen
Indicates how an action, event, or situation is classified or characterized under a specific legal framework or set of laws.
- F. None of above.
Provenance (3 batches)
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_69efd6b340f0819095680e15dcdc1830 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f64235bd948190ad4051682fc8a8ca |
completed | May 2, 2026, 6:28 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10:12 p.m.