Triple

T14557286
Position Surface form Disambiguated ID Type / Status
Subject Ravensbourne (UK Parliament constituency) E341572 entity
Predicate boundaryChangeYear P21193 FINISHED
Object 1983 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: 1983 | Statement: [Ravensbourne (UK Parliament constituency), boundaryChangeYear, 1983]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: boundaryChangeYear
Context triple: [Ravensbourne (UK Parliament constituency), boundaryChangeYear, 1983]
  • A. transitionYear
    Indicates the specific year in which a change, shift, or transition from one state, condition, or phase to another occurs.
  • B. borderChange chosen
    Indicates a change in the boundaries between geographic or political entities, such as when borders are redrawn, expanded, reduced, or otherwise altered over time.
  • C. redesignationYear
    Indicates the year in which something was officially redesignated, renamed, or assigned a new status or classification.
  • D. dateChangesWith
    Indicates that the date associated with one entity is altered or updated in conjunction with, or as a result of, a change involving another entity.
  • E. banYear
    Indicates the year in which a ban was enacted or came into effect on the related entity or activity.
  • 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_69d822db9c8481908213ceb39585f792 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb2f1490881908673f429e5288c86 completed April 14, 2026, 9:34 p.m.
PD Predicate disambiguation batch_69de5c57489c8190b57917be1dba6ae6 completed April 14, 2026, 3:25 p.m.
Created at: April 10, 2026, 1:23 a.m.