Triple
T20476326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bermondsey Abbey |
E502326
|
entity |
| Predicate | denominationBeforeReformation |
P61912
|
FINISHED |
| Object | Catholic |
—
|
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: Catholic | Statement: [Bermondsey Abbey, denominationBeforeReformation, Catholic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denominationBeforeReformation Context triple: [Bermondsey Abbey, denominationBeforeReformation, Catholic]
-
A.
denominationReform
Indicates a change or restructuring in a religious denomination’s doctrines, practices, or organizational form.
-
B.
historicalDenomination
chosen
Indicates that an entity was formerly associated with or belonged to a particular denomination or sect at some point in the past.
-
C.
religionBeforeReformation
Indicates that an entity’s religious affiliation or practice existed or was established prior to the historical period known as the Reformation.
-
D.
currencyDuringReign
Indicates the type of currency that was in use during the period of a specific ruler’s reign.
-
E.
denominationFounded
Indicates that one entity established or created a particular religious denomination.
- 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_69e0b4af32848190aea80682b44d5d6e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6996584648190a1a6dfcb57782b7f |
completed | April 20, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69e5768372988190b08ef8ae67d42ab6 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:34 a.m.