Triple

T37746620
Position Surface form Disambiguated ID Type / Status
Subject St Paul’s Church, Jarrow E940859 entity
Predicate notableFigureBuriedOrCommemorated P3803 FINISHED
Object Venerable Bede E57880 NE 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: Venerable Bede | Statement: [St Paul’s Church, Jarrow, notableFigureBuriedOrCommemorated, Venerable Bede]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notableFigureBuriedOrCommemorated
Context triple: [St Paul’s Church, Jarrow, notableFigureBuriedOrCommemorated, Venerable Bede]
  • A. reputedBurialPlaceOf
    Indicates a location that is widely believed or traditionally thought to be the burial place of a particular person or group.
  • B. alsoBurials
    Indicates that the subject location or record includes additional burial sites or burial events beyond the primary one referenced.
  • C. notablePersonDiedHere
    Indicates that a notable or famous person died at the referenced location.
  • D. cemeteryKnownFor
    Indicates that a cemetery is notable or recognized for a particular person, event, feature, or characteristic.
  • E. hasNotableBurials chosen
    Indicates that a place, typically a cemetery or burial site, contains the graves or remains of individuals considered notable or significant.
  • F. None of above.

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_69f76ee0e32c8190b40a3b4cf590337c completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_6a037c8efcd4819088c2aeead65d93df completed May 12, 2026, 7:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a410cafec0c819082c03086e2371907 completed June 28, 2026, 11:59 a.m.
PD Predicate disambiguation batch_6a037a1772e48190ba738c6d11b321e2 completed May 12, 2026, 7:05 p.m.
Created at: May 3, 2026, 4:19 p.m.