Triple
T28169810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artikel 43 Grondwet |
E715424
|
entity |
| Predicate | betrekkingOp |
P120650
|
FINISHED |
| Object | benoemingsprocedure van leden van de regering |
—
|
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: benoemingsprocedure van leden van de regering | Statement: [Artikel 43 Grondwet, betrekkingOp, benoemingsprocedure van leden van de regering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: betrekkingOp Context triple: [Artikel 43 Grondwet, betrekkingOp, benoemingsprocedure van leden van de regering]
-
A.
verwantAan
Indicates that one entity is related or connected to another, typically through some form of kinship, association, or conceptual similarity.
-
B.
betreft
chosen
Indicates that something concerns, relates to, or is about something or someone.
-
C.
повʼязанеЗ
Indicates a general association or connection between one entity and another.
-
D.
subjectRelation
Indicates that one entity stands in a specified relational role or connection to another entity.
-
E.
usedToRelate
Indicates that one entity previously had a relationship or association with another, but that relationship no longer holds in the present.
- 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_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 10:12 p.m.