Triple
T17950353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Home Rule Bill |
E448815
|
entity |
| Predicate | voteOutcomeInCommons |
P10095
|
FINISHED |
| Object | passed after multiple divisions |
—
|
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: passed after multiple divisions | Statement: [Second Home Rule Bill, voteOutcomeInCommons, passed after multiple divisions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voteOutcomeInCommons Context triple: [Second Home Rule Bill, voteOutcomeInCommons, passed after multiple divisions]
-
A.
resultedInParliament
Indicates that one event, action, or situation caused or led to the formation, change, or outcome of a specific parliament.
-
B.
voteResult
chosen
Indicates the outcome or decision produced by a voting process involving the related entities.
-
C.
labourPopularVoteShare
Indicates the proportion of all valid votes cast that were received by the Labour Party in a given election or electoral contest.
-
D.
LabourSeatsWon
Indicates the number of parliamentary seats won by the Labour Party in an election.
-
E.
referendumResult
Indicates the outcome or decision reached by voters in a specific referendum.
- 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_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. |
Created at: April 10, 2026, 10:21 a.m.