Triple
T1268757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord of Parliament |
E15661
|
entity |
| Predicate | preUnionParliamentMembership |
P20999
|
FINISHED |
| Object | hereditary |
—
|
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: hereditary | Statement: [Lord of Parliament, preUnionParliamentMembership, hereditary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preUnionParliamentMembership Context triple: [Lord of Parliament, preUnionParliamentMembership, hereditary]
-
A.
hasMemberOfParliament
Indicates that an entity is represented by a specific individual serving as its Member of Parliament.
-
B.
previousParliament
Indicates that one parliament directly preceded another in chronological order.
-
C.
servedInParliamentFor
Indicates that a person held a parliamentary seat as a representative of a specified constituency, region, or jurisdiction.
-
D.
areRepresentedIn
Indicates that one entity serves as a representation, depiction, or encoding of another entity within a given medium, context, or system.
-
E.
parliamentaryStatus
chosen
Indicates the relationship of whether and how an entity is formally recognized or holds standing within a parliamentary system or body.
- 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_69a4935a94308190bb92555b79032824 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4c03aaa8c8190bacb7de5a38329da |
completed | March 1, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69a4bede52a081909665d60acbe41d31 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.