Triple

T28174275
Position Surface form Disambiguated ID Type / Status
Subject 2016 United Kingdom European Union membership referendum E715546 entity
Predicate votesForRemain P63379 FINISHED
Object 16141241 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: 16141241 | Statement: [2016 United Kingdom European Union membership referendum, votesForRemain, 16141241]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: votesForRemain
Context triple: [2016 United Kingdom European Union membership referendum, votesForRemain, 16141241]
  • A. votesOnly
    Indicates that an entity participates in a decision-making process solely by casting votes, without engaging in any other associated actions or roles.
  • B. voteRecord
    Indicates that an entity has cast a specific vote or holds a particular voting position in a given decision or election.
  • C. votesForChange
    Indicates that an entity expresses support for or chooses an option aimed at altering an existing state, policy, or condition.
  • D. voteCount chosen
    Indicates the number of votes that have been cast for or associated with a particular item or option.
  • E. voteResult
    Indicates the outcome or decision produced by a voting process involving the related entities.
  • 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_69efd6b340f0819095680e15dcdc1830 completed April 27, 2026, 9:35 p.m.
NER Named-entity recognition batch_69f6562fd3488190be1acd8c526a28d2 completed May 2, 2026, 7:53 p.m.
PD Predicate disambiguation batch_69f651a931748190a637e631a52bbfaa completed May 2, 2026, 7:34 p.m.
Created at: April 27, 2026, 10:15 p.m.