Triple
T28169803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artikel 43 Grondwet |
E715424
|
entity |
| Predicate | maaktDeelUitVanHoofdstuk |
P6720
|
FINISHED |
| Object | Hoofdstuk 2 van de Grondwet |
—
|
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: Hoofdstuk 2 van de Grondwet | Statement: [Artikel 43 Grondwet, maaktDeelUitVanHoofdstuk, Hoofdstuk 2 van de Grondwet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maaktDeelUitVanHoofdstuk Context triple: [Artikel 43 Grondwet, maaktDeelUitVanHoofdstuk, Hoofdstuk 2 van de Grondwet]
-
A.
containsChapter
chosen
Indicates that one entity (typically a larger work or document) includes another entity as a chapter within its structure.
-
B.
chapterOn
Indicates that one entity (typically a chapter) is about, discusses, or focuses on the subject represented by another entity.
-
C.
chapterName
Indicates that a chapter is identified or labeled by a specific name or title.
-
D.
chapterMentioned
Indicates that a specific chapter is referenced or cited within a given context or source.
-
E.
containsSubchapter
Indicates that one chapter or section includes another, more specific subchapter as a part of its structure.
- 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.