Triple

T22661258
Position Surface form Disambiguated ID Type / Status
Subject Becontree E559666 entity
Predicate neighbourhoodType P19245 FINISHED
Object predominantly residential 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: predominantly residential | Statement: [Becontree, neighbourhoodType, predominantly residential]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: neighbourhoodType
Context triple: [Becontree, neighbourhoodType, predominantly residential]
  • A. notableNeighborhoodType chosen
    Indicates that a neighborhood is notably characterized by, or strongly associated with, a particular type or category (e.g., residential, commercial, historic).
  • B. neighborhood
    Indicates that one entity is located in close spatial proximity to another, typically within the same local area or district.
  • C. typicalNeighborhoods
    Indicates that the associated neighborhoods are characteristic or commonly found examples for the given entity or context.
  • D. hasNeighbourhood
    Indicates that one entity is located within, or is associated with, a particular neighborhood area of another entity.
  • E. neighborhoodCharacteristic
    Indicates that a particular characteristic, feature, or quality is associated with or describes a given neighborhood.
  • 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_69e2454a158c819093b8e35f5045efb6 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f1765fe7d081908087778c54c1e612 completed April 29, 2026, 3:09 a.m.
PD Predicate disambiguation batch_69ee6294c4c08190b7e4829f4b9af24b completed April 26, 2026, 7:08 p.m.
Created at: April 17, 2026, 3:07 p.m.