Triple

T25786743
Position Surface form Disambiguated ID Type / Status
Subject Foster Lane, City of London E649438 entity
Predicate inPostcodeArea P920 FINISHED
Object EC4 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: EC4 | Statement: [Foster Lane, City of London, inPostcodeArea, EC4]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: inPostcodeArea
Context triple: [Foster Lane, City of London, inPostcodeArea, EC4]
  • A. hasPostcodeDistrictCode
    Indicates that an entity is associated with a specific postcode district code within a postal addressing system.
  • B. hasPostcodeSector
    Indicates that an entity is associated with a specific postcode sector within a postal addressing system.
  • C. postalArea chosen
    Indicates that one entity is the postal or ZIP code area associated with the location or address represented by the other entity.
  • D. hasPostcodeDistrictsApprox
    Indicates that one entity is associated with a set of postcode districts in an approximate or non-exact manner.
  • E. postalAreaIncludes
    Indicates that a given postal area geographically contains or covers another specified location or region.
  • 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_69e7ab33e9308190afe415dc6f9e8876 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f5fefb52508190b6201334ad5b0477 completed May 2, 2026, 1:41 p.m.
PD Predicate disambiguation batch_69f4a0fed15881909b789251fe5d8d45 completed May 1, 2026, 12:47 p.m.
Created at: April 22, 2026, 5:55 a.m.