Triple
T6747757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Lords (as a life peer’s wife) |
E154260
|
entity |
| Predicate | relatedStatus |
P59172
|
FINISHED |
| Object | spouse of a member of Parliament |
—
|
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: spouse of a member of Parliament | Statement: [House of Lords (as a life peer’s wife), relatedStatus, spouse of a member of Parliament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedStatus Context triple: [House of Lords (as a life peer’s wife), relatedStatus, spouse of a member of Parliament]
-
A.
associatedStatus
Indicates that one entity is linked to or characterized by a particular status or condition.
-
B.
associatedPeopleStatus
chosen
Indicates the role, condition, or standing of people who are connected or linked to a given entity or event.
-
C.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
D.
laterRelationWith
Indicates that one entity stands in a temporal relationship to another such that it occurs or exists at a later time than the other.
-
E.
relatedTo
Indicates a general, non-specific relationship or association exists between two 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_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.