Triple
T6747721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Lords (as a life peer’s wife) |
E154260
|
entity |
| Predicate | associatedWithTitleType |
P5175
|
FINISHED |
| Object | life peerage |
—
|
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: life peerage | Statement: [House of Lords (as a life peer’s wife), associatedWithTitleType, life peerage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithTitleType Context triple: [House of Lords (as a life peer’s wife), associatedWithTitleType, life peerage]
-
A.
associatedTitle
chosen
Indicates that one entity has a title, designation, or formal label that is linked or relevant to another entity.
-
B.
relatedTitleHolder
Indicates that one entity holds a title or position that is related or connected to the title or position held by another entity.
-
C.
associatedTitleCreation
Indicates that one entity is linked to the creation or origination of a particular title associated with another entity.
-
D.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
E.
associatedName
Indicates that one entity has an alternative or related name that is linked or connected to 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_69c6880ef37881909268a5a7299b9293 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d1d785dc81909c033084d2068568 |
completed | March 27, 2026, 6:52 p.m. |
| PD | Predicate disambiguation | batch_69c6d09067a0819087ed6c820f4699f8 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:11 p.m.