Triple
T31904693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meaningful vote on the Brexit withdrawal agreement (March 29, 2019) |
E814515
|
entity |
| Predicate | voteNumber |
P63379
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Meaningful vote on the Brexit withdrawal agreement (March 29, 2019), voteNumber, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voteNumber Context triple: [Meaningful vote on the Brexit withdrawal agreement (March 29, 2019), voteNumber, 3]
-
A.
voteCount
chosen
Indicates the number of votes that have been cast for or associated with a particular item or option.
-
B.
voteType
Indicates the specific category or kind of vote associated with an action or decision (e.g., upvote, downvote, approval, rejection).
-
C.
voteOn
Indicates that an entity formally expresses a choice or decision regarding a specific proposal, issue, or candidate.
-
D.
voteSource
Indicates the origin or basis from which a vote is derived or recorded.
-
E.
votesOnly
Indicates that an entity participates in a decision-making process solely by casting votes, without engaging in any other associated actions or roles.
- 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b1b2be408190bef7834aa16578a8 |
completed | May 3, 2026, 2:23 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: May 1, 2026, midnight