Triple
T33720309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle Claydon, Buckinghamshire |
E863991
|
entity |
| Predicate | historicallyTiedToEstate |
P78227
|
FINISHED |
| Object | Claydon 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: Claydon estate | Statement: [Middle Claydon, Buckinghamshire, historicallyTiedToEstate, Claydon estate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyTiedToEstate Context triple: [Middle Claydon, Buckinghamshire, historicallyTiedToEstate, Claydon estate]
-
A.
hasNearbyHistoricalEstate
Indicates that one entity is located close to another entity that is a recognized historical estate.
-
B.
hadEstates
Indicates that an entity possessed or owned one or more estates (properties or landholdings).
-
C.
historicallyAssociatedHouse
chosen
Indicates that there is a historical connection or association between an entity and a particular house, such as residence, ownership, or significant events tied to that location.
-
D.
estateTypeHistorically
Indicates that one entity historically had a particular type or classification of estate, even if that estate type may have changed or no longer exists in the present.
-
E.
associatedWithHistoricHome
Indicates a relationship in which an entity is connected or linked in some relevant way to a historic home.
- 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_69f34989871c81908682e22a2fe4b829 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a00144238708190acbec3f791cc873e |
completed | May 10, 2026, 5:14 a.m. |
| PD | Predicate disambiguation | batch_6a00120244a4819090ef39070aba9d99 |
completed | May 10, 2026, 5:05 a.m. |
Created at: May 1, 2026, 1:44 a.m.