Triple
T36000653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broadlands |
E1041119
|
entity |
| Predicate | hasParkAndGardenDesignation |
P64297
|
FINISHED |
| Object | Grade II* registered park and garden |
—
|
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: Grade II* registered park and garden | Statement: [Broadlands, hasParkAndGardenDesignation, Grade II* registered park and garden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParkAndGardenDesignation Context triple: [Broadlands, hasParkAndGardenDesignation, Grade II* registered park and garden]
-
A.
hasParkAndGardenRegister
Indicates that an entity is recorded in an official register of parks and gardens.
-
B.
hasParkAndGardenGrade
chosen
Indicates that an entity has been assigned a specific quality or rating level for its parks and gardens.
-
C.
parkDesignation
Indicates that an area or location has been officially designated or classified as a park.
-
D.
hasBotanicalGarden
Indicates that one entity possesses, contains, or includes a botanical garden as part of its facilities or domain.
-
E.
hasLakeGarden
Indicates that an entity possesses or includes a garden that features or is centered around a lake.
- 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_69f76e2a02208190aedd1f9025a8b300 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffef812da48190b875a7376b24f92d |
completed | May 10, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69ffedecd580819097851b1473fdd6ed |
completed | May 10, 2026, 2:31 a.m. |
Created at: May 3, 2026, 4:07 p.m.