Triple
T28169798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artikel 43 Grondwet |
E715424
|
entity |
| Predicate | bevoegdGezag |
P164089
|
FINISHED |
| Object | Koning |
—
|
NE NERFINISHED |
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: Koning | Statement: [Artikel 43 Grondwet, bevoegdGezag, Koning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bevoegdGezag Context triple: [Artikel 43 Grondwet, bevoegdGezag, Koning]
-
A.
rechtskracht
Indicates that a legal decision, rule, or act has binding legal force and is formally effective and enforceable.
-
B.
actedUnderAuthorityOf
Indicates that one entity performed actions under the direction, control, or legal authority of another entity.
-
C.
liegeTo
Indicates a feudal or hierarchical relationship in which one party owes allegiance, service, or loyalty to another as their superior or lord.
-
D.
exercisedPowerOver
Indicates that one entity exerted control, influence, or authority over another entity.
-
E.
hasVoivodeshipRights
Indicates that an entity possesses the legal status, privileges, or jurisdictional authority associated with a voivodeship (a regional administrative unit).
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 10:12 p.m.