Triple
T7680416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ständerat |
E173976
|
entity |
| Predicate | presidingOfficerTermLength |
P540
|
FINISHED |
| Object | 1 year |
—
|
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: 1 year | Statement: [Ständerat, presidingOfficerTermLength, 1 year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presidingOfficerTermLength Context triple: [Ständerat, presidingOfficerTermLength, 1 year]
-
A.
electsTermLength
Indicates the length of time for which an entity is elected to hold a particular position or office.
-
B.
termLength
chosen
Indicates the duration or period of time for which an agreement, position, or condition remains in effect.
-
C.
termInOffice
Indicates the period during which an individual officially holds a particular office or position.
-
D.
presidingOfficerForCount
Indicates that a particular officer has official responsibility for overseeing or presiding over a specific count (such as a charge, claim, or item) within a legal or procedural context.
-
E.
parliamentaryTerm
Indicates the specific legislative session or fixed period of time during which a parliament is formally in office and exercises its authority.
- 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_69c6995840408190a19de6c51090f46f |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7048b0b448190889bd40e0a38e51a |
completed | March 27, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69c701618d3481908be84b76f36ac5a1 |
completed | March 27, 2026, 10:14 p.m. |
Created at: March 27, 2026, 4:01 p.m.