Triple
T8164607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artikel 42 Grondwet |
E190658
|
entity |
| Predicate | categorie |
P87
|
FINISHED |
| Object | organisatie van het staatsbestel |
—
|
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: organisatie van het staatsbestel | Statement: [Artikel 42 Grondwet, categorie, organisatie van het staatsbestel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: categorie Context triple: [Artikel 42 Grondwet, categorie, organisatie van het staatsbestel]
-
A.
category
chosen
Indicates that one entity is classified as a member or type within the grouping or class defined by another entity.
-
B.
catalog
Indicates the action of systematically listing, organizing, or recording items or information into a structured collection or database.
-
C.
categoryLabel_N
Indicates that an entity is assigned a specific categorical label or classification name.
-
D.
textCategory
Indicates that a piece of text belongs to or is classified under a particular category or type.
-
E.
canonicalCategory
Indicates that an entity is assigned to its primary or standard category within a classification system.
- 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_69ca82c0ef14819083713f4473dd847c |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4664fef881908b0dc7b158aca398 |
completed | March 31, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69cb36a4c40c81909f60aef0e1624c13 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:38 p.m.