Triple

T27517153
Position Surface form Disambiguated ID Type / Status
Subject St Wilfrid's Church, Ribchester E694599 entity
Predicate isBuiltNear P21298 FINISHED
Object site of Roman fort Bremetennacum 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: site of Roman fort Bremetennacum | Statement: [St Wilfrid's Church, Ribchester, isBuiltNear, site of Roman fort Bremetennacum]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isBuiltNear
Context triple: [St Wilfrid's Church, Ribchester, isBuiltNear, site of Roman fort Bremetennacum]
  • A. builtNear chosen
    Indicates that one entity was constructed at a location geographically close to another entity.
  • B. hasMainBuildingNear
    Indicates that the primary or central building associated with an entity is located in close physical proximity to another specified entity or place.
  • C. hasNearbyCivicBuilding
    Indicates that one entity is located close to, or in the immediate vicinity of, a civic building such as a government, public service, or community facility.
  • D. hasNeighboringBuilding
    Indicates that one building is located adjacent to or directly next to another building.
  • E. hasNearbyInfrastructureType
    Indicates that an entity is located close to infrastructure of a specified type.
  • 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_69ef53842afc8190ba6bd4e4999bda67 completed April 27, 2026, 12:16 p.m.
NER Named-entity recognition batch_69f62efda4cc8190973e1874e98c5ad5 completed May 2, 2026, 5:06 p.m.
PD Predicate disambiguation batch_69f623aaf40081909f947431424a1d55 completed May 2, 2026, 4:17 p.m.
Created at: April 27, 2026, 1:19 p.m.