Triple
T27261692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Buccleuch |
E687782
|
entity |
| Predicate | formerEstate |
P3526
|
FINISHED |
| Object | Dalkeith Palace |
—
|
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: Dalkeith Palace | Statement: [House of Buccleuch, formerEstate, Dalkeith Palace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerEstate Context triple: [House of Buccleuch, formerEstate, Dalkeith Palace]
-
A.
heirOfEstate
Indicates that one entity is legally designated to inherit the estate or property of another entity, typically upon that entity’s death.
-
B.
occupiesFormerEstateOf
chosen
Indicates that one entity currently resides in, uses, or controls a property that was previously the estate of another entity.
-
C.
hadEstate
Indicates that an entity possessed or owned a particular estate or landed property.
-
D.
grandfatherEstateOf
Indicates that one entity is the estate or inherited property originating from the grandfather of another entity.
-
E.
laterFunctionOfEstate
Indicates that one function or role of an estate occurs at a later time or stage relative to another function of that same estate.
- 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_69ef3557abc481908bf3c146f0f3356a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: April 27, 2026, 10:53 a.m.