Triple
T25238028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilson governments |
E632388
|
entity |
| Predicate | electoralMandate |
P7692
|
FINISHED |
| Object | 1964 United Kingdom general election |
—
|
NE NERFINISHED |
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: 1964 United Kingdom general election | Statement: [Wilson governments, electoralMandate, 1964 United Kingdom general election]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electoralMandate Context triple: [Wilson governments, electoralMandate, 1964 United Kingdom general election]
-
A.
typeOfElectoralMandate
Indicates the specific kind or category of electoral mandate associated with an office, position, or representative.
-
B.
мандат
Indicates that an entity holds an official mandate or authority to act or represent others in a specific role or context.
-
C.
electoralSuccess
chosen
Indicates that an entity has achieved a favorable or winning outcome in an election or electoral process.
-
D.
electoralBasis
Indicates the principle, rule, or criterion by which representatives or officials are chosen in an election.
-
E.
electoralPurpose
Indicates that something is intended, designed, or used for the purposes of an election or electoral process.
- 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 21, 2026, 1:07 p.m.