Triple
T1097090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lords Spiritual in the House of Lords |
E24293
|
entity |
| Predicate | canVote |
P6119
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Lords Spiritual in the House of Lords, canVote, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canVote Context triple: [Lords Spiritual in the House of Lords, canVote, true]
-
A.
canVoteOn
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.
-
B.
votingAge
Indicates the minimum age at which an individual is legally permitted to vote.
-
C.
eligibleVoters
chosen
Indicates that the referenced entities are legally permitted and qualified to vote in a given election or jurisdiction.
-
D.
canElect
Indicates that one entity has the authority or ability to choose another entity for a position, role, or office through an election process.
-
E.
usesElectoralRight
Indicates that an entity exercises its electoral rights, such as voting or otherwise participating in an electoral process.
- 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_69a4940542308190ac2a0b1f730b7cfc |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9a1d3108190b2a304fef429848d |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b7448c148190a3c9a4158ebd05b4 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.