Triple
T27415063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cluniac priory |
E692869
|
entity |
| Predicate | followsReformOf |
P136696
|
FINISHED |
| Object | Cluniac reform |
—
|
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: Cluniac reform | Statement: [Cluniac priory, followsReformOf, Cluniac reform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsReformOf Context triple: [Cluniac priory, followsReformOf, Cluniac reform]
-
A.
followedEarlierReform
Indicates that one entity adopted or implemented a reform at an earlier time than another entity did.
-
B.
isPartOfReform
Indicates that an action, measure, or component belongs to, contributes to, or is included within a broader reform initiative or process.
-
C.
replacedInReform
Indicates that one entity was substituted or superseded by another as part of a formal reform or restructuring process.
-
D.
associatedReform
chosen
Indicates a relationship where one entity is linked to, connected with, or involved in a particular reform or set of reforms.
-
E.
subjectToReformBy
Indicates that an entity is undergoing or designated for changes, improvements, or restructuring carried out by another entity.
- 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_69ef5208617081908f731d312e0fd1bc |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 27, 2026, 12:33 p.m.