Triple
T28734476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belgian regional elections |
E730756
|
entity |
| Predicate | datePattern |
P20585
|
FINISHED |
| Object | usually held in June |
—
|
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: usually held in June | Statement: [Belgian regional elections, datePattern, usually held in June]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: datePattern Context triple: [Belgian regional elections, datePattern, usually held in June]
-
A.
dateFormat
Indicates the specific pattern or structure used to represent a date as a formatted string.
-
B.
dateNotation
Indicates how a date is written or formatted in notation (e.g., order and style of day, month, and year).
-
C.
notationPattern
Indicates a recurring way in which something is symbolically represented or written, such as a consistent style or structure of notation used for an entity or concept.
-
D.
languagePattern
Indicates a recurring or structured way in which language is used, organized, or formed within a given context.
-
E.
observancePattern
chosen
Indicates how an action, rule, or practice is regularly carried out or followed over time, such as its schedule, frequency, or customary pattern of observance.
- 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_69f043eae0908190b28ce314686247d7 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6576a87648190a48a42a50d9925c6 |
completed | May 2, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 6 a.m.