Triple
T24796315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sidney family |
E620392
|
entity |
| Predicate | hasHereditaryEstate |
P8997
|
FINISHED |
| Object | Penshurst Place estate |
—
|
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: Penshurst Place estate | Statement: [Sidney family, hasHereditaryEstate, Penshurst Place estate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHereditaryEstate Context triple: [Sidney family, hasHereditaryEstate, Penshurst Place estate]
-
A.
hasHereditaryRights
Indicates that one entity possesses rights or privileges that are passed down through family lineage or inheritance from another entity.
-
B.
hasHereditaryChief
Indicates that an entity is led or governed by a chief whose position is inherited through family lineage.
-
C.
hasHereditaryOffice
Indicates that an entity holds an office or position that is passed down through family lineage rather than acquired by election, appointment, or merit.
-
D.
hadEstate
chosen
Indicates that an entity possessed or owned a particular estate or landed property.
-
E.
hasHereditaryDesignation
Indicates that an entity possesses a title, status, or designation that is passed down through family lineage or inheritance.
- 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_69e2fabe77c8819085f7ce6486248139 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 18, 2026, 4:48 a.m.