Triple
T28476726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miljoenennota |
E720582
|
entity |
| Predicate | isCentralToEvent |
P4408
|
FINISHED |
| Object | begrotingsdebat in de Tweede Kamer |
—
|
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: begrotingsdebat in de Tweede Kamer | Statement: [Miljoenennota, isCentralToEvent, begrotingsdebat in de Tweede Kamer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCentralToEvent Context triple: [Miljoenennota, isCentralToEvent, begrotingsdebat in de Tweede Kamer]
-
A.
isCentralTo
chosen
Indicates that something plays a primary, essential, or defining role in relation to something else, such that the latter depends on or is organized around it.
-
B.
isCentralObjectIn
Indicates that an entity serves as the primary or focal object within a specified context, structure, or collection.
-
C.
isLinkedToEvent
Indicates that an entity has an association or connection with a specific event.
-
D.
isPremierEventIn
Indicates that an event is recognized as the primary or most important event within a specified context, location, or series.
-
E.
isCentreOf
Indicates that one entity serves as the central point, core, or focal location relative to another entity or context.
- 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_69f01a5983f48190b7c1b8857245a4f7 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 2:52 a.m.