Triple
T27512933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westminster conservation area |
E694466
|
entity |
| Predicate | planningConstraint |
P152930
|
FINISHED |
| Object | controls on demolition |
—
|
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: controls on demolition | Statement: [Westminster conservation area, planningConstraint, controls on demolition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planningConstraint Context triple: [Westminster conservation area, planningConstraint, controls on demolition]
-
A.
hasPlanningConstraint
chosen
Indicates that there is a rule, limitation, or condition that must be considered when planning or scheduling an activity, resource, or process.
-
B.
designedToConstrain
Indicates that one entity is intentionally created or configured to limit, restrict, or control the behavior, range, or properties of another entity.
-
C.
constrainedBy
Indicates that one entity’s state, behavior, or possibilities are limited, restricted, or governed by another entity.
-
D.
planningRequirement
Indicates that one entity imposes or specifies a planning-related obligation, condition, or prerequisite that must be satisfied by another entity or activity.
-
E.
solutionConstraint
Indicates that a solution must satisfy a specified condition, limitation, or requirement within a given 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_69ef53842afc8190ba6bd4e4999bda67 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 27, 2026, 1:17 p.m.