Triple
T25238118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Callaghan government |
E632390
|
entity |
| Predicate | lostVoteOfConfidence |
P158060
|
FINISHED |
| Object | 1979-03-28 |
—
|
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: 1979-03-28 | Statement: [Callaghan government, lostVoteOfConfidence, 1979-03-28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostVoteOfConfidence Context triple: [Callaghan government, lostVoteOfConfidence, 1979-03-28]
-
A.
heldConfidenceVoteIn
Indicates that a confidence vote was conducted within a specified governing body, assembly, or context.
-
B.
voteAgainst
Indicates that an entity formally expresses opposition to a proposal, decision, or candidate in a voting process.
-
C.
lostElectoralDignityTo
Indicates that one political figure or entity lost an electoral position, title, or honor to another in an election or similar voting process.
-
D.
reasonForLossOfVote
Indicates the specific cause or circumstance that led to an entity losing its right or ability to vote.
-
E.
lostFormalVoteOnBudget
Indicates that an entity failed to secure enough support in a formal vote on a budget proposal.
- 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f47dfc523c8190b61295b451d1e5cd |
completed | May 1, 2026, 10:18 a.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 21, 2026, 1:07 p.m.