Triple
T20458358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Birkenhead |
E501854
|
entity |
| Predicate | seatChamberType |
P76754
|
FINISHED |
| Object | upper house |
—
|
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: upper house | Statement: [Baron Birkenhead, seatChamberType, upper house]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seatChamberType Context triple: [Baron Birkenhead, seatChamberType, upper house]
-
A.
chamberType
Indicates the specific kind or category of chamber associated with an entity (e.g., room, compartment, or enclosed space type).
-
B.
typeOfChamber
chosen
Indicates the specific kind or category of chamber that an entity belongs to or is classified as.
-
C.
seatCategory
Indicates the classification or type of a seat (e.g., by comfort level, price tier, or section) assigned to an entity.
-
D.
seatStructure
Indicates that one entity serves as the structural or physical seating component or arrangement associated with another entity.
-
E.
seatLocation
Indicates the spatial position or placement of a seat relative to a reference point or environment.
- 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_69e0b4ad4940819098cf2ff6413574e5 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e696a2a8a88190992211b09295d8ea |
completed | April 20, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:33 a.m.