Triple
T590971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Lords Act 1999 |
E17268
|
entity |
| Predicate | allowedHereditaryPeersToRemain |
P273
|
FINISHED |
| Object | 92 |
—
|
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: 92 | Statement: [House of Lords Act 1999, allowedHereditaryPeersToRemain, 92]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowedHereditaryPeersToRemain Context triple: [House of Lords Act 1999, allowedHereditaryPeersToRemain, 92]
-
A.
additionalMembersAllowed
Indicates that more members are permitted to be added beyond those already included or initially specified.
-
B.
grantedTo
Indicates that a right, permission, or resource has been formally given or assigned by one party to another.
-
C.
allowedNonPartyCandidates
Indicates that candidates who are not affiliated with any recognized party are permitted to participate in a given electoral process or contest.
-
D.
allows
chosen
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
-
E.
associatedHeir
Indicates that one entity is designated or recognized as the heir connected to, or inheriting from, another entity.
- 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_69a49379d09c8190ac7e00b24e2810b1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49bb8ff0081909cd53d88930e2693 |
completed | March 1, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69a494cc13988190892ca10bd7ae9f09 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.