Triple
T8712988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wolterton Park |
E206823
|
entity |
| Predicate | hasLandscapeDesignPeriod |
P14116
|
FINISHED |
| Object | 18th century |
—
|
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: 18th century | Statement: [Wolterton Park, hasLandscapeDesignPeriod, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLandscapeDesignPeriod Context triple: [Wolterton Park, hasLandscapeDesignPeriod, 18th century]
-
A.
hasLandscapeDesignInfluence
Indicates that one entity has influenced or shaped the landscape design style, principles, or features of another entity.
-
B.
hasDesignPeriod
chosen
Indicates that something was created, planned, or developed during a specified historical or stylistic design period.
-
C.
designPeriod
Indicates the time span during which something is planned, designed, or conceptually developed before implementation or production.
-
D.
hasLandscaping
Indicates that an entity possesses or is associated with designed outdoor grounds or landscape features.
-
E.
partOfHistoricLandscapeDesign
Indicates that something is included within, or contributes to, a historically significant landscape design as one of its constituent elements.
- 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_69ca83572d4881909bef3be2b578d539 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5cd522a88190a32facd86206af66 |
completed | March 31, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69cc456e806c819087e7d66ee737f242 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:35 p.m.