Triple

T12536445
Position Surface form Disambiguated ID Type / Status
Subject Martlesham Heath E299701 entity
Predicate hasPlanningType P105780 FINISHED
Object new village 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: new village development | Statement: [Martlesham Heath, hasPlanningType, new village development]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPlanningType
Context triple: [Martlesham Heath, hasPlanningType, new village development]
  • A. hasPlanningStatus
    Indicates that an entity is associated with a particular stage, condition, or outcome in a planning or approval process.
  • B. hasPlanningCharacteristic
    Indicates that an entity possesses a specific feature, quality, or attribute related to planning activities or processes.
  • C. hasPlanningPattern
    Indicates that an entity follows or is associated with a particular planning pattern or structured approach to planning.
  • D. hasPlanningAssociation
    Indicates a relationship where one entity is involved with, linked to, or considered in the planning or preparation activities of another entity.
  • E. hasPlanningLevel
    Indicates that an entity is associated with a specific stage, tier, or granularity within a planning or scheduling hierarchy.
  • 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_69d6ada707008190aaec1238117c9379 completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d95f5507b481908d13cc317b7402f6 completed April 10, 2026, 8:36 p.m.
PD Predicate disambiguation batch_69d9540d7b788190a0d57b098e90e491 completed April 10, 2026, 7:48 p.m.
PDg Predicate description generation batch_69d95f5148948190946a575d812b329d completed April 10, 2026, 8:36 p.m.
Created at: April 8, 2026, 9:57 p.m.