Triple

T16867252
Position Surface form Disambiguated ID Type / Status
Subject Deanery of Christ Church, Oxford E410073 entity
Predicate instanceOf P0 FINISHED
Object building in Oxford C22576 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: building in Oxford
Context triple: [Deanery of Christ Church, Oxford, instanceOf, building in Oxford]
  • A. University of Oxford building chosen
    A University of Oxford building is a physical structure owned, leased, or formally used by the University of Oxford for academic, administrative, residential, or support purposes within its collegiate and institutional framework.
  • B. University of Cambridge building
    A University of Cambridge building is a physical structure owned, leased, or used by the University of Cambridge for academic, administrative, residential, research, or support purposes within the collegiate university environment.
  • C. district of Oxford
    A district of Oxford is an administrative or geographic subdivision of the city, characterized by its own local identity, land use patterns, and community services within the broader urban area of Oxford.
  • D. college of the University of Oxford
    A college of the University of Oxford is a self-governing academic community within the university that provides teaching, accommodation, and social and pastoral support to its students and fellows.
  • E. bridge over the River Cam
    A bridge over the River Cam is a structure that spans the river to connect its banks, enabling pedestrians, cyclists, or vehicles to cross while often serving as a notable architectural and cultural landmark in the surrounding landscape.
  • F. None of above.

Provenance (1 batch)

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_69d88395e6c88190b22730f335107c14 completed April 10, 2026, 4:59 a.m.
Created at: April 10, 2026, 5:24 a.m.