Triple
T6423553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aylesbury (UK Parliament constituency) |
E128001
|
entity |
| Predicate | hasInPersonVoting |
P70793
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Aylesbury (UK Parliament constituency), hasInPersonVoting, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInPersonVoting Context triple: [Aylesbury (UK Parliament constituency), hasInPersonVoting, yes]
-
A.
voteCountedIn
Indicates that a particular vote has been included in the official tally for a specific election, contest, or jurisdiction.
-
B.
hasPrepollVoting
Indicates that an election or voting event includes the option for voters to cast their ballots before the official polling day.
-
C.
hasElection
Indicates that an entity conducts, holds, or is associated with an election event.
-
D.
hasVotingPower
Indicates that an entity possesses the authority or capacity to participate in a decision-making or electoral process by casting votes.
-
E.
votingIs
Indicates that an entity is engaged in, characterized by, or involved in the act or process of voting.
- 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_69c00838de888190af2eec0b80495efa |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c06906eea88190a445c1ff1169c2b1 |
completed | March 22, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69c060f780b08190aa650b4d1fc51f21 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c062d290448190a2183158ef75d129 |
completed | March 22, 2026, 9:44 p.m. |
Created at: March 22, 2026, 4:43 p.m.