Triple
T981455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harewood House |
E21176
|
entity |
| Predicate | hasLandscapeGarden |
P12538
|
FINISHED |
| Object | Capability Brown-designed landscape |
—
|
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: Capability Brown-designed landscape | Statement: [Harewood House, hasLandscapeGarden, Capability Brown-designed landscape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLandscapeGarden Context triple: [Harewood House, hasLandscapeGarden, Capability Brown-designed landscape]
-
A.
hasLandscaping
Indicates that an entity possesses or is associated with designed outdoor grounds or landscape features.
-
B.
hasGardenType
chosen
Indicates that an entity possesses or is associated with a garden of a specified type.
-
C.
landscapeDesignedBy
Indicates that a particular landscape or outdoor environment was planned, created, or shaped by a specific designer or design entity.
-
D.
landscapeStyle
Indicates the design style or aesthetic approach applied to a landscape or outdoor environment.
-
E.
landscapeType
Indicates the kind or category of natural terrain or scenery that characterizes a place or area.
- 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_69a493c2b62c8190b616351789ec47f8 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b47cbca48190a01880bb411e80bd |
completed | March 1, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69a4b2aa219081908a6b0ef786b4aa52 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:41 p.m.