Triple
T22667798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solesmes Abbey |
E559837
|
entity |
| Predicate | suppressionDate |
P28109
|
FINISHED |
| Object | 1791 |
—
|
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: 1791 | Statement: [Solesmes Abbey, suppressionDate, 1791]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suppressionDate Context triple: [Solesmes Abbey, suppressionDate, 1791]
-
A.
dateOfSuppression
Indicates the specific date on which something (such as information, a record, or a right) was formally suppressed, withheld, or made inactive.
-
B.
suspensionDate
Indicates the date on which an entity’s normal status, operation, or privileges are formally suspended.
-
C.
cessationDate
Indicates the date on which an ongoing state, activity, or relationship comes to an end.
-
D.
suppressedOn
Indicates that one entity is intentionally prevented, hidden, or blocked from being shown, executed, or taking effect in the context of another entity.
-
E.
suppressionYear
chosen
Indicates the year in which the referenced activity, expression, or entity was formally suppressed, halted, or forcibly discontinued.
- 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.