Triple
T528811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish representative peers in House of Lords |
E10982
|
entity |
| Predicate | hasVotingRight |
P1084
|
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: [Scottish representative peers in House of Lords, hasVotingRight, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVotingRight Context triple: [Scottish representative peers in House of Lords, hasVotingRight, yes]
-
A.
votingAge
Indicates the minimum age at which an individual is legally permitted to vote.
-
B.
canVoteOn
chosen
Indicates that an entity has the right or permission to participate in a decision-making process by casting a vote on a specific item, issue, or proposal.
-
C.
eligibleVoters
Indicates that the referenced entities are legally permitted and qualified to vote in a given election or jurisdiction.
-
D.
hasFederalElectorate
Indicates that an entity is associated with a specific federal electoral district that represents it in a national legislative body.
-
E.
hasElectorate
Indicates that a political representative, office, or governing body is associated with and serves a specific group of voters or electoral district.
- 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1d39b4c81909f265b3501b5ec1d |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f01ac3ec8190a94a05955532c7fa |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.