Triple
T941792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cherkley Court |
E20321
|
entity |
| Predicate | ownershipHistory |
P22003
|
FINISHED |
| Object | privately owned estate |
—
|
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: privately owned estate | Statement: [Cherkley Court, ownershipHistory, privately owned estate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownershipHistory Context triple: [Cherkley Court, ownershipHistory, privately owned estate]
-
A.
hasDenominationHistory
Indicates that an entity has an associated record or sequence of changes in its denomination over time.
-
B.
hasFireHistory
Indicates that an entity has experienced one or more fire events in the past.
-
C.
upgradeHistory
Indicates the record of changes where one version, state, or configuration has been replaced or improved by another over time.
-
D.
hasHistoricalAttribution
Indicates that something is credited, assigned, or linked to a person, group, or source based on historical records or tradition.
-
E.
historicallyBorneBy
Indicates that an entity has carried, possessed, or used another entity (such as a name, title, or symbol) at some point in the past.
- F. None of above. chosen
Provenance (4 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_69a493b0270c81909e6c9ce310f6aa55 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3a1a4888190997adf56eb761431 |
completed | March 1, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69a4b29c68f48190aecad10e351a99de |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b344f6f48190ba03ce593c94176b |
completed | March 1, 2026, 9:44 p.m. |
Created at: March 1, 2026, 7:40 p.m.