Triple
T18872559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian parliamentary elections |
E461607
|
entity |
| Predicate | fixedTerm |
P133281
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Norwegian parliamentary elections, fixedTerm, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fixedTerm Context triple: [Norwegian parliamentary elections, fixedTerm, yes]
-
A.
termFixedBy
Indicates that a term is determined, constrained, or made unchangeable by another entity or condition.
-
B.
signedContractLength
Indicates the duration or term length specified in a contract that has been formally signed between parties.
-
C.
appointedForFixedTerm
Indicates that an entity has been formally assigned to a role or position for a specified, limited duration.
-
D.
termStructure
Indicates a hierarchical or compositional organization of terms, showing how smaller term units are structurally related to form larger expressions.
-
E.
hasNoFixedTermLength
Indicates that the relationship or agreement exists without a predetermined or fixed duration for how long it will remain in effect.
- F. None of above. chosen
Provenance (4 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c2aa9074819092137d236df3717b |
completed | April 20, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69e48d22dde8819093b1d963bd673365 |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:57 a.m.