Triple

T18966819
Position Surface form Disambiguated ID Type / Status
Subject European Parliament elections in Poland E464061 entity
Predicate appliesThresholdTo P14326 FINISHED
Object party lists 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: party lists | Statement: [European Parliament elections in Poland, appliesThresholdTo, party lists]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: appliesThresholdTo
Context triple: [European Parliament elections in Poland, appliesThresholdTo, party lists]
  • A. thresholdFor chosen
    Indicates that one entity specifies the minimum or limiting value at which a condition, effect, or state involving another entity begins to occur or change.
  • B. appliesOver
    Indicates that one entity’s effect, rule, or condition extends across or is valid for a specified range, domain, or set of entities.
  • C. appliesFrom
    Indicates that a rule, condition, or effect begins to be applicable starting from a specific point in time or state.
  • D. appliesIf
    Indicates that a rule, condition, or operation is applicable only when certain specified criteria or circumstances are met.
  • E. appliesAt
    Indicates that an action, rule, or condition is relevant to or in effect at a specific location, context, or point in time.
  • 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_69d8dcffc278819086792a4ebfddfafa completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d5d7183c8190b1258c0381233efd completed April 20, 2026, 7:29 a.m.
PD Predicate disambiguation batch_69e4a2f437648190b85650dae8885d48 completed April 19, 2026, 9:40 a.m.
Created at: April 10, 2026, noon