Triple

T4039582
Position Surface form Disambiguated ID Type / Status
Subject Westminster City Council E83911 entity
Predicate establishedAsLondonBoroughCouncilOn P35022 FINISHED
Object 1965 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: 1965 | Statement: [Westminster City Council, establishedAsLondonBoroughCouncilOn, 1965]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: establishedAsLondonBoroughCouncilOn
Context triple: [Westminster City Council, establishedAsLondonBoroughCouncilOn, 1965]
  • A. createdAsLondonBorough chosen
    Indicates that an entity was formally established or designated with the status of a London borough.
  • B. hasBoroughCouncil
    Indicates that an administrative area is governed or overseen by a specific borough council.
  • C. hasLondonAssemblyConstituency
    Indicates that an entity is associated with a specific London Assembly constituency as its designated electoral or administrative area.
  • D. hasOuterLondonBorough
    Indicates that an entity is associated with, located in, or administered by a borough that is part of Outer London.
  • E. boroughOf
    Indicates that one place is a borough that is administratively or geographically part of another, typically larger, municipal entity.
  • 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_69aed92f7cf0819098e0539bdcc3767f completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefb37e24c81908d6357ab8ba5388d completed March 9, 2026, 4:54 p.m.
PD Predicate disambiguation batch_69aef900386481909d04555a9ec9b0e3 completed March 9, 2026, 4:44 p.m.
Created at: March 9, 2026, 3:37 p.m.