Triple
T22667796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solesmes Abbey |
E559837
|
entity |
| Predicate | reformedAsBenedictineAbbey |
P11203
|
FINISHED |
| Object | 11th 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: 11th century | Statement: [Solesmes Abbey, reformedAsBenedictineAbbey, 11th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reformedAsBenedictineAbbey Context triple: [Solesmes Abbey, reformedAsBenedictineAbbey, 11th century]
-
A.
refoundedAsBenedictineMonastery
chosen
Indicates that something was re-established or reorganized specifically as a Benedictine monastery.
-
B.
formerCistercianAbbey
Indicates that something was once a Cistercian abbey but no longer holds that status.
-
C.
foundedAsConventFor
Indicates that an institution or building was originally established specifically to serve as a convent for a particular religious community or group.
-
D.
reformedOn
Indicates that an entity underwent a reform, change, or restructuring at a specific point in time or on a particular date.
-
E.
laterReformedAs
Indicates that an entity was subsequently reorganized, renamed, or transformed into another entity at a later time.
- 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_69e2454a158c819093b8e35f5045efb6 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1781ceca08190ba1309570e81c5af |
completed | April 29, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:09 p.m.