Triple

T23673341
Position Surface form Disambiguated ID Type / Status
Subject Landseer Road conservation area E584794 entity
Predicate hasPlanningConstraint P152930 FINISHED
Object additional planning controls on development 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: additional planning controls on development | Statement: [Landseer Road conservation area, hasPlanningConstraint, additional planning controls on development]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPlanningConstraint
Context triple: [Landseer Road conservation area, hasPlanningConstraint, additional planning controls on development]
  • A. hasPlanningType
    Indicates that an entity is associated with a specific category or type used for planning or scheduling purposes.
  • B. hasRecreationConstraint
    Indicates a restriction or limitation placed on how recreation or leisure activities may occur or be used.
  • C. hasPlanningAssociation
    Indicates a relationship where one entity is involved with, linked to, or considered in the planning or preparation activities of another entity.
  • D. hasPlanningCharacteristic
    Indicates that an entity possesses a specific feature, quality, or attribute related to planning activities or processes.
  • E. hasPlanningStatus
    Indicates that an entity is associated with a particular stage, condition, or outcome in a planning or approval process.
  • F. None of above. chosen

Provenance (4 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_69e24901421881908c17a5293bdd4a8e completed April 17, 2026, 2:51 p.m.
NER Named-entity recognition batch_69f1b410bd788190b2c6853e13287ace completed April 29, 2026, 7:32 a.m.
PD Predicate disambiguation batch_69f118dd13008190a8799b4e9cadbd79 completed April 28, 2026, 8:30 p.m.
PDg Predicate description generation batch_69f121cc494081908c987adfcde89b0e completed April 28, 2026, 9:08 p.m.
Created at: April 17, 2026, 6:51 p.m.