Triple
T30531851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viscount Malpas |
E777025
|
entity |
| Predicate | seatAssociatedWithSeniorTitle |
P16984
|
FINISHED |
| Object | Houghton Hall, Norfolk |
—
|
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: Houghton Hall, Norfolk | Statement: [Viscount Malpas, seatAssociatedWithSeniorTitle, Houghton Hall, Norfolk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seatAssociatedWithSeniorTitle Context triple: [Viscount Malpas, seatAssociatedWithSeniorTitle, Houghton Hall, Norfolk]
-
A.
hasSeatTitle
Indicates that an entity holds a position or seat identified by a specific title.
-
B.
seatOwnedBy
Indicates that a particular seat is possessed or held in ownership by a specific entity.
-
C.
seatGrantedBy
Indicates that a position, seat, or place (e.g., in a body or venue) is conferred or allocated to someone or something by a specific granting authority or entity.
-
D.
seatTraditionallyAssociated
chosen
Indicates that one entity is a seat or position that is customarily or historically linked with another entity, such as a role, office, or title.
-
E.
seatName
Indicates the specific name or label assigned to a seat associated with an 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_69f2249c11508190ae7e955755ccfb01 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6884ceb18819082e8c4002d1faa95 |
completed | May 2, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:18 p.m.