Triple
T17950309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Home Rule Bill |
E448814
|
entity |
| Predicate | defeatedByMargin |
P129855
|
FINISHED |
| Object | 30 votes |
—
|
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: 30 votes | Statement: [First Home Rule Bill, defeatedByMargin, 30 votes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defeatedByMargin Context triple: [First Home Rule Bill, defeatedByMargin, 30 votes]
-
A.
finalRoundMargin
Indicates the point or score difference between competitors in the final round of a contest or competition.
-
B.
defeatedCandidate
Indicates that one candidate has won an election or contest against another candidate, causing the other to lose.
-
C.
popularVoteMargin
Indicates the difference in the number or percentage of popular votes received by two candidates or options in an election.
-
D.
marginOfVictoryElectoralVotes
Indicates the difference in the number of electoral votes between the winning and losing candidates or parties in an election.
-
E.
defeatedBy
Indicates that one entity has been beaten, overcome, or conquered by another in a contest, conflict, or competition.
- 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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4afab8d988190b6c06d7406fb64c1 |
completed | April 19, 2026, 10:34 a.m. |
| PD | Predicate disambiguation | batch_69e3f8f2bd088190b1e22ad4d9cc8b13 |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:21 a.m.