Triple

T38274103
Position Surface form Disambiguated ID Type / Status
Subject Restalrig E1021296 entity
Predicate hasNotableSite P2462 FINISHED
Object St Triduana’s Chapel
St Triduana’s Chapel is a historic medieval religious structure in Restalrig, Edinburgh, traditionally associated with the cult of the early Christian saint Triduana.
E2263538 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: St Triduana’s Chapel | Statement: [Restalrig, hasNotableSite, St Triduana’s Chapel]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: St Triduana’s Chapel
Triple: [Restalrig, hasNotableSite, St Triduana’s Chapel]
Generated description
St Triduana’s Chapel is a historic medieval religious structure in Restalrig, Edinburgh, traditionally associated with the cult of the early Christian saint Triduana.

Provenance (5 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_69f76dee198c8190bf5109421e47a658 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fcc58e639881908b82d4c3641e27ff completed May 7, 2026, 5:02 p.m.
NED1 Entity disambiguation (via context triple) batch_6a4193dcf7088190b982723c072b4f5c completed June 28, 2026, 9:36 p.m.
NEDg Description generation batch_6a419562557c81909280edd7d755f959 completed June 28, 2026, 9:42 p.m.
NED2 Entity disambiguation (via description) batch_6a4195c696f8819096e040b28883213b completed June 28, 2026, 9:44 p.m.
Created at: May 3, 2026, 4:30 p.m.