Triple

T4048600
Position Surface form Disambiguated ID Type / Status
Subject See of York E84127 entity
Predicate traditionallyClaimsFoundationIn P53810 FINISHED
Object 7th century 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: 7th century | Statement: [See of York, traditionallyClaimsFoundationIn, 7th century]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: traditionallyClaimsFoundationIn
Context triple: [See of York, traditionallyClaimsFoundationIn, 7th century]
  • A. claimsFoundationBy
    Indicates that one entity asserts or declares that another entity serves as its basis, origin, or underlying foundation.
  • B. foundationalTraditionFor
    Indicates that one tradition serves as a fundamental basis or source upon which another tradition is built or developed.
  • C. heritageClaimedBy
    Indicates that a particular heritage, tradition, or cultural legacy is asserted or identified as belonging to a specific entity.
  • D. foundedUnder
    Indicates that an entity was established or created during the tenure, authority, or jurisdiction of another entity (such as a leader, regime, or governing body).
  • E. hasFoundation
    Indicates that an entity is supported, established, or based upon a particular foundation or underlying basis.
  • F. None of above. chosen

Provenance (4 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_69aed930bd5c819083e7dcc14fc44f69 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefb82d1a08190aa8c5c48d368b58b completed March 9, 2026, 4:55 p.m.
PD Predicate disambiguation batch_69aef900386481909d04555a9ec9b0e3 completed March 9, 2026, 4:44 p.m.
PDg Predicate description generation batch_69aef98ed84c81909dc86097df4afd4f completed March 9, 2026, 4:47 p.m.
Created at: March 9, 2026, 3:37 p.m.