Triple

T30244518
Position Surface form Disambiguated ID Type / Status
Subject Spira E769018 entity
Predicate associatedWithImperialCathedral GENERATED
Object Speyer Cathedral UNRECOGNIZED GENERATED

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.

PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: associatedWithImperialCathedral
Context triple: [Spira, associatedWithImperialCathedral, Speyer Cathedral]
  • A. associatedWithCathedral chosen
    Indicates a relationship in which an entity has a connection or involvement with a cathedral, such as location, affiliation, use, or historical linkage.
  • B. associatedWithPalace
    Indicates a relationship where an entity has a connection, link, or involvement with a palace, such as through location, function, ownership, or affiliation.
  • C. usesCathedralFor
    Indicates that an entity employs or makes use of a cathedral for a particular purpose or activity.
  • D. associatedWithEmperor
    Indicates a relationship in which an entity has a connection, link, or affiliation with an emperor, such as through service, influence, kinship, or shared authority.
  • E. coCathedral
    Indicates that a church shares the status and functions of a cathedral with another cathedral within the same diocese or ecclesiastical jurisdiction.
  • 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_69f224831dc08190b2e569b987264057 completed April 29, 2026, 3:32 p.m.
Created at: April 29, 2026, 7:39 p.m.