Triple
T30329165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baroness Masham of Ilton |
E771425
|
entity |
| Predicate | titleHolderChamber |
P139801
|
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: [Baroness Masham of Ilton, titleHolderChamber, House of Lords]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHolderChamber Context triple: [Baroness Masham of Ilton, titleHolderChamber, House of Lords]
-
A.
titleHolderDuring
Indicates that one entity holds a specific title or position during a defined time period in relation to another entity.
-
B.
titleHolderParliamentaryHouse
chosen
Indicates that a person holds an official title or position within a specific parliamentary house.
-
C.
titleHolderUnder
Indicates that one entity holds a title, position, or rank under the authority, jurisdiction, or hierarchy of another entity.
-
D.
titleHolderIs
Indicates that one entity currently holds or possesses a specific title associated with another entity.
-
E.
titleHolderWas
Indicates that an entity previously held a specific title or position before it passed to someone or something else.
- 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_69f2248aba24819095bb86480d55b23b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
Created at: April 29, 2026, 7:53 p.m.