Triple
T31954866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Reed of Allermuir |
E815875
|
entity |
| Predicate | grantsMembershipIn |
P34367
|
FINISHED |
| Object | House of Lords |
—
|
NE NERFINISHED |
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: House of Lords | Statement: [Baron Reed of Allermuir, grantsMembershipIn, House of Lords]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantsMembershipIn Context triple: [Baron Reed of Allermuir, grantsMembershipIn, House of Lords]
-
A.
confersMembershipIn
chosen
Indicates that one entity grants or bestows membership status in a group, organization, or category upon another entity.
-
B.
impliesMembershipIn
Indicates that one entity logically entails or asserts that another entity belongs to a particular group, set, or category.
-
C.
membershipIn
Indicates that an entity belongs to, is part of, or holds membership in a particular group, organization, or collection.
-
D.
killsMembersOf
Indicates that one entity causes the death of individuals who belong to a particular group or organization.
-
E.
memberOfGroupWith
Indicates that an entity belongs to, or is associated as a member with, a particular group or collection of entities.
- 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: May 1, 2026, 12:08 a.m.