Triple
T29448005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Easton Royal, Wiltshire |
E746901
|
entity |
| Predicate | hasFormerReligiousHouse |
P186965
|
FINISHED |
| Object | Easton Priory |
—
|
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: Easton Priory | Statement: [Easton Royal, Wiltshire, hasFormerReligiousHouse, Easton Priory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerReligiousHouse Context triple: [Easton Royal, Wiltshire, hasFormerReligiousHouse, Easton Priory]
-
A.
hasFormerReligiousCommunity
Indicates that an entity previously belonged to a particular religious community but is no longer a member of it.
-
B.
hasFormerReligiousJurisdiction
Indicates that an entity was previously under the religious authority or governance of another entity, but no longer is.
-
C.
formerReligiousAffiliation
Indicates that an entity previously adhered to a particular religion or religious denomination but no longer does so.
-
D.
hasReligiousMovement
Indicates that an entity is associated with, follows, or is characterized by a particular religious movement.
-
E.
hasAssociatedReligion
Indicates that an entity is connected with or linked to a particular religion.
- 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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fb2e9309fc81909dfefd9020d6fbad |
completed | May 6, 2026, 12:05 p.m. |
Created at: April 28, 2026, 3:29 p.m.