Triple
T30536467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suckley family |
E777160
|
entity |
| Predicate | propertyStewardship |
P106566
|
FINISHED |
| Object | Wilderstein 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: Wilderstein estate | Statement: [Suckley family, propertyStewardship, Wilderstein estate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propertyStewardship Context triple: [Suckley family, propertyStewardship, Wilderstein estate]
-
A.
estateManagementActivity
chosen
Indicates activities involved in administering, maintaining, or overseeing an estate or property and its associated affairs.
-
B.
property
Indicates that one entity possesses, is characterized by, or has an attribute or quality associated with another entity.
-
C.
propertyHeld
Indicates that a particular property is possessed, owned, or controlled by a specified entity.
-
D.
managesPropertyFor
Indicates that one entity is responsible for overseeing, operating, or administering a property on behalf of another entity.
-
E.
estateManaged
Indicates that one entity is responsible for administering, overseeing, or handling the affairs and assets of another entity’s 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_69f2249d183c8190b79937c1768d2163 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 29, 2026, 8:18 p.m.