Triple
T1004767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chamber of Deputies (Luxembourg) |
E21683
|
entity |
| Predicate | electoralFrequency |
P2971
|
FINISHED |
| Object | every 5 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: every 5 years | Statement: [Chamber of Deputies (Luxembourg), electoralFrequency, every 5 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electoralFrequency Context triple: [Chamber of Deputies (Luxembourg), electoralFrequency, every 5 years]
-
A.
legislativePeriodicity
Indicates how frequently a legislative body or process recurs or is scheduled to occur over time.
-
B.
electionCycle
chosen
Indicates the recurring period or sequence of time in which elections are organized, conducted, and repeated for a given office or political system.
-
C.
electoralAlliancePeriod
Indicates the time span during which two or more political entities are formally joined in an electoral alliance.
-
D.
electionNumber
Indicates the specific ordinal or identifying number assigned to a particular election within a series or system of elections.
-
E.
electoralBasis
Indicates the principle, rule, or criterion by which representatives or officials are chosen in an election.
- 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_69a493c53e648190ae8cb76c433fd9a7 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b51303548190a5ee3c0797fc3245 |
completed | March 1, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69a4b2b2e7108190b338b6c19d4aff55 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:41 p.m.