Triple
T33149721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Buckinghamshire |
E848401
|
entity |
| Predicate | hasFamilySeatLocation |
P146899
|
FINISHED |
| Object | 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: Norfolk | Statement: [Earl of Buckinghamshire, hasFamilySeatLocation, Norfolk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilySeatLocation Context triple: [Earl of Buckinghamshire, hasFamilySeatLocation, Norfolk]
-
A.
hasFamilySeatNear
chosen
Indicates that an entity’s principal family residence or ancestral seat is located in the vicinity of another specified place or entity.
-
B.
hasPrioritySeating
Indicates that one entity provides or designates reserved or preferential seating for another entity.
-
C.
hasSeatAt
Indicates that an entity occupies or holds a place, position, or membership within a specific group, body, or location.
-
D.
hasSeatStatus
Indicates the current condition or availability state of a seat in a given context.
-
E.
hasSeat
Indicates that one entity possesses, provides, or includes a seat for 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_69f3495a458c8190a1d34b237ba0be3f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
Created at: May 1, 2026, 1:28 a.m.