Triple

T10128471
Position Surface form Disambiguated ID Type / Status
Subject Metropolitan Green Belt E226274 entity
Predicate allowsDevelopmentType P2224 FINISHED
Object limited infilling in villages 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: limited infilling in villages | Statement: [Metropolitan Green Belt, allowsDevelopmentType, limited infilling in villages]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: allowsDevelopmentType
Context triple: [Metropolitan Green Belt, allowsDevelopmentType, limited infilling in villages]
  • A. hasDevelopmentType chosen
    Indicates the type or category of development associated with an entity, such as the nature, form, or stage of its development.
  • B. canDevelop
    Indicates that one entity has the ability or capacity to develop, create, or build another entity.
  • C. hasDevelopmentStatus
    Indicates the current stage or condition of progress or completion that something is in.
  • D. hasDevelopmentSystem
    Indicates that one entity possesses, uses, or is associated with a particular system, platform, or environment used for development activities.
  • E. hasDevelopmentDimension
    Indicates that something possesses or is associated with a particular aspect or dimension of development.
  • 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_69ca843057b48190a86730167f5d6b98 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cdd2f0a0e881909267a83fbeb31f0c completed April 2, 2026, 2:22 a.m.
PD Predicate disambiguation batch_69cd4ba1d360819087698d04a53cc87e completed April 1, 2026, 4:45 p.m.
Created at: March 30, 2026, 9:05 p.m.