Triple
T14256771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aldermaston Court |
E353403
|
entity |
| Predicate | hasParkAndGardenStatus |
P87030
|
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: [Aldermaston Court, hasParkAndGardenStatus, Grade II registered park and garden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParkAndGardenStatus Context triple: [Aldermaston Court, hasParkAndGardenStatus, Grade II registered park and garden]
-
A.
hasParkAndGardenGrade
Indicates that an entity has been assigned a specific quality or rating level for its parks and gardens.
-
B.
hasParkAndGardenRegister
chosen
Indicates that an entity is recorded in an official register of parks and gardens.
-
C.
hasParkStatus
Indicates that an entity holds a particular designation or status related to being a park (e.g., national park, city park, protected parkland).
-
D.
hasParkArea
Indicates that an entity includes or is associated with a designated park or recreational area within its boundaries.
-
E.
hasParkAccess
Indicates that an entity is permitted to enter, use, or otherwise access a specified park or park 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de62992a188190bc046fbab5a149d6 |
completed | April 14, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69de2a7d586c8190846ff242bbf5ac53 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:09 a.m.