Triple
T25409319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medeshamstede Abbey |
E636644
|
entity |
| Predicate | hasSaintlyAssociation |
P43509
|
FINISHED |
| Object | Saint Peter |
—
|
NE NERFINISHED |
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: Saint Peter | Statement: [Medeshamstede Abbey, hasSaintlyAssociation, Saint Peter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSaintlyAssociation Context triple: [Medeshamstede Abbey, hasSaintlyAssociation, Saint Peter]
-
A.
hasReligiousFigureAssociation
Indicates a relationship in which an entity is connected or linked to a religious figure, such as through dedication, representation, influence, or affiliation.
-
B.
hasReligiousCharismAssociatedWith
Indicates that an entity possesses or is identified with a particular religious charism, spiritual gift, or distinctive spiritual focus associated with another entity.
-
C.
linkedToSaint
chosen
Indicates that one entity has a direct association or connection with a saint.
-
D.
hasPatronSaint
Indicates that one entity serves as the patron saint associated with, protecting, or representing another entity.
-
E.
typeOfSaint
Indicates that one entity is classified as a specific kind or category of saint in relation to another entity.
- 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_69e75db361d881908d8701c856da6413 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 21, 2026, 1:52 p.m.