Triple
T412979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bath Abbey |
E9530
|
entity |
| Predicate | refoundedAsBenedictineMonastery |
P11203
|
FINISHED |
| Object | 10th 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: 10th century | Statement: [Bath Abbey, refoundedAsBenedictineMonastery, 10th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refoundedAsBenedictineMonastery Context triple: [Bath Abbey, refoundedAsBenedictineMonastery, 10th century]
-
A.
refoundedBy
Indicates that an entity was re-established or reconstituted by another entity after a period of inactivity, dissolution, or significant change.
-
B.
numberOfActiveMonasteries
Indicates the count of monasteries that are currently active or operational in a given context.
-
C.
foundedAs
Indicates the original name or form under which an organization, institution, or entity was first established.
-
D.
consecratedBy
Indicates that one entity has been formally made sacred, dedicated, or set apart for religious use through a ritual or act performed by another entity.
-
E.
religiousAffiliationAtFoundation
Indicates the religious denomination or tradition with which an entity was affiliated at the time it was founded.
- 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_69a2e80111fc8190961d5b7c6154123f |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ecdc422881908910428fd1aee7c6 |
completed | Feb. 28, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69a2e9749234819084b0ce94faabd0b1 |
completed | Feb. 28, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69a2ea60e590819081779a6510918d9b |
completed | Feb. 28, 2026, 1:15 p.m. |
Created at: Feb. 28, 2026, 1:09 p.m.