Triple
T24184217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abbot Samson of Bury St Edmunds |
E599507
|
entity |
| Predicate | areaOfReform |
P88043
|
FINISHED |
| Object | monastic discipline |
—
|
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: monastic discipline | Statement: [Abbot Samson of Bury St Edmunds, areaOfReform, monastic discipline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areaOfReform Context triple: [Abbot Samson of Bury St Edmunds, areaOfReform, monastic discipline]
-
A.
reformsArea
chosen
Indicates that an entity is responsible for changing, improving, or restructuring a particular area or domain.
-
B.
typeOfReforms
Indicates the specific kinds or categories of reforms associated with an entity or situation.
-
C.
reform
Indicates bringing about significant changes to an existing system, practice, or entity in order to improve or correct it.
-
D.
goalOfReforms
Indicates that a reform or set of reforms is undertaken with the aim or intended objective of achieving a particular outcome.
-
E.
associatedReforms
Indicates a relationship where certain reforms are linked or connected to a given entity, such as a policy, event, or individual.
- 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_69e288cca05481908faeb1563711114a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:35 p.m.