Triple
T32220861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bedford Park, London |
E823058
|
entity |
| Predicate | conservationAreaDesignation |
P103372
|
FINISHED |
| Object | 1967 |
—
|
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: 1967 | Statement: [Bedford Park, London, conservationAreaDesignation, 1967]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conservationAreaDesignation Context triple: [Bedford Park, London, conservationAreaDesignation, 1967]
-
A.
environmentDesignation
Indicates that an entity is assigned a specific environmental classification or status within a given context.
-
B.
establishedAsConservationArea
chosen
Indicates that a location or region has been officially designated and protected as a conservation area.
-
C.
cityPlanningDesignation
Indicates how an area is officially classified or designated within urban or municipal planning (e.g., residential, commercial, industrial).
-
D.
parkDesignation
Indicates that an area or location has been officially designated or classified as a park.
-
E.
earthDesignation
Indicates that an entity has a specific name or label assigned to it for use in an Earth-based or human-centric context.
- 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_69f3490b4f948190b99e4f999f5be25f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: May 1, 2026, 12:38 a.m.