Triple
T28443077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandleford Priory, Berkshire |
E715764
|
entity |
| Predicate | foundedAsPrioryInCentury |
P1824
|
FINISHED |
| Object | 12th 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: 12th century | Statement: [Sandleford Priory, Berkshire, foundedAsPrioryInCentury, 12th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsPrioryInCentury Context triple: [Sandleford Priory, Berkshire, foundedAsPrioryInCentury, 12th century]
-
A.
wasMonasticCentreFromCentury
Indicates that a place functioned as a monastic center starting from a specified century.
-
B.
hasPrioryChurch
Indicates that an entity possesses or is associated with a specific priory church as part of its properties or domain.
-
C.
abbeyFoundedInYearApprox
Indicates that an abbey was founded around an approximate year, rather than on a precisely known date.
-
D.
wasEcclesiasticalCentreUntilCentury
Indicates that a place functioned as an ecclesiastical (church or religious) center up to, but not beyond, a specified century.
-
E.
foundedInCentury
chosen
Indicates that an entity was established or came into existence during a specified century.
- 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_69efd6b44550819094ae991b553d9fc3 |
completed | April 27, 2026, 9:35 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. |
Created at: April 28, 2026, 1:47 a.m.