Triple
T11631197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German federal elections |
E276401
|
entity |
| Predicate | regularInterval |
P63472
|
FINISHED |
| Object | every 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: every 4 years | Statement: [German federal elections, regularInterval, every 4 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regularInterval Context triple: [German federal elections, regularInterval, every 4 years]
-
A.
intervalAct
Indicates an action or relationship that occurs over, or is defined by, a specific time interval between entities.
-
B.
hasInterval
chosen
Indicates that something is associated with a specific span or range between two points in time, space, or value.
-
C.
rotationPeriod_hours
Indicates the length of time, measured in hours, that an object takes to complete one full rotation on its axis.
-
D.
originalTimeInterval
Indicates the initial or primary time span during which an event, state, or relationship is considered to occur, before any adjustments or derived intervals.
-
E.
dosingInterval
Indicates the time period that should elapse between consecutive doses of a medication or treatment.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a25aa9188190ab13d79139f37e7e |
completed | April 10, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.