Triple
T5177224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centre Party (Norway) |
E116828
|
entity |
| Predicate | coreVoterBase |
P3251
|
FINISHED |
| Object | farmers |
—
|
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: farmers | Statement: [Centre Party (Norway), coreVoterBase, farmers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreVoterBase Context triple: [Centre Party (Norway), coreVoterBase, farmers]
-
A.
voterFunction
Indicates a relationship where an entity serves in the role or capacity of a voter within a decision-making or electoral process.
-
B.
publicVoteWeight
Indicates that an entity’s influence or impact in a public voting process is quantified by a specific weight or value.
-
C.
votingBasis
Indicates the principle, criterion, or grounds on which a vote or voting decision is made.
-
D.
votingControl
Indicates that one entity has the power to determine or significantly influence the outcome of decisions made by another entity through its voting rights.
-
E.
electoralBase
chosen
Indicates the group of voters or supporters that primarily backs or sustains a particular candidate, party, or political movement in elections.
- 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_69bd446140f08190becb93c61158f27f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7974a5308190819b100e07189131 |
completed | March 20, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69bd77b529948190b86671ebe43f4734 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:45 p.m.