Triple
T1724822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belgian federal elections |
E37472
|
entity |
| Predicate | termLengthOfChamber |
P540
|
FINISHED |
| Object | 4 years |
—
|
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: 4 years | Statement: [Belgian federal elections, termLengthOfChamber, 4 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: termLengthOfChamber Context triple: [Belgian federal elections, termLengthOfChamber, 4 years]
-
A.
termLength
chosen
Indicates the duration or period of time for which an agreement, position, or condition remains in effect.
-
B.
parliamentaryTerm
Indicates the specific legislative session or fixed period of time during which a parliament is formally in office and exercises its authority.
-
C.
legislativeTermNumber
Indicates the ordinal number assigned to a specific legislative term within a sequence of legislative periods.
-
D.
legislativePeriod
Indicates the specific legislative term or session during which an action, event, or status is valid or took place.
-
E.
numberOfLegislativeChambers
Indicates the quantity of distinct legislative chambers that a given political or legislative body possesses.
- 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_69a8861acab88190bb43cde203429399 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aadb7bda1081908f2c41c520c9c55c |
completed | March 6, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69aa61c0a0288190bce9d60062a84b69 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.