Triple

T28419109
Position Surface form Disambiguated ID Type / Status
Subject Artikel 68 Grondwet E719890 entity
Predicate beperking P1050 FINISHED
Object kan worden beperkt door het belang van de staat 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: kan worden beperkt door het belang van de staat | Statement: [Artikel 68 Grondwet, beperking, kan worden beperkt door het belang van de staat]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: beperking
Context triple: [Artikel 68 Grondwet, beperking, kan worden beperkt door het belang van de staat]
  • A. restriction chosen
    Indicates a limiting condition or rule that constrains or controls what an entity can do, use, or access in relation to another entity or context.
  • B. limitaCon
    Indicates that one entity imposes a restriction, constraint, or limit on another entity or its behavior.
  • C. hadRestrictionsOn
    Indicates that one entity imposed or was subject to specific limitations, rules, or constraints regarding another entity or activity.
  • D. prohibits
    Indicates that one entity forbids or disallows another entity from performing a specific action or being in a certain state.
  • E. notableRestriction
    Indicates that there is a significant limitation, constraint, or prohibition that meaningfully affects the entity or its use.
  • 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_69eff6f1c5088190bc24bfbf92f9c017 completed April 27, 2026, 11:53 p.m.
NER Named-entity recognition batch_69f64dc3ba8c81909c5ccae79102cde7 completed May 2, 2026, 7:17 p.m.
PD Predicate disambiguation batch_69f641e2f1708190b45b48d6a43c51d2 completed May 2, 2026, 6:26 p.m.
Created at: April 28, 2026, 1:32 a.m.