Triple
T30536472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suckley family |
E777160
|
entity |
| Predicate | hasHistoricHome |
P72352
|
FINISHED |
| Object | Wilderstein Historic Site |
—
|
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 Historic Site | Statement: [Suckley family, hasHistoricHome, Wilderstein Historic Site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricHome Context triple: [Suckley family, hasHistoricHome, Wilderstein Historic Site]
-
A.
hasHistoricPremises
Indicates that an entity possesses or is associated with premises that have historical significance or heritage value.
-
B.
hasHistoricHut
Indicates that an entity possesses, contains, or is associated with a historic hut.
-
C.
associatedWithHistoricHome
chosen
Indicates a relationship in which an entity is connected or linked in some relevant way to a historic home.
-
D.
hasHomeRegionHistorical
Indicates that an entity is historically associated with or originates from a particular home region.
-
E.
hasHistoricKit
Indicates that an entity possesses or is associated with a historically significant version or design of a kit (e.g., uniform, equipment set, or standard set of items).
- 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_69fdd07a34c08190982b8c61c2775cf6 |
completed | May 8, 2026, noon |
| PD | Predicate disambiguation | batch_69fdbd25c7908190b72fca8de7ce503f |
completed | May 8, 2026, 10:38 a.m. |
Created at: April 29, 2026, 8:18 p.m.