Triple
T7199844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concluding Rites |
E168711
|
entity |
| Predicate | typicalDismissalFormula |
P35592
|
FINISHED |
| Object | “Go forth, the Mass is ended.” |
—
|
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: “Go forth, the Mass is ended.” | Statement: [Concluding Rites, typicalDismissalFormula, “Go forth, the Mass is ended.”]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDismissalFormula Context triple: [Concluding Rites, typicalDismissalFormula, “Go forth, the Mass is ended.”]
-
A.
reasonForDismissal
Indicates the cause or justification for which an entity (such as a person, case, or item) was dismissed, terminated, or removed.
-
B.
typicalConclusion
Indicates that one entity is the usual or expected outcome, result, or ending that follows from another entity or situation.
-
C.
couldBeDismissedBy
Indicates that one entity has the authority or power to terminate, remove, or discharge the other from a position, role, or obligation.
-
D.
closingFormula
chosen
Indicates the conventional closing phrase or formula used to end a communication, such as a letter, email, or message.
-
E.
finalDisposition
Indicates the ultimate outcome, status, or resolution assigned to an entity after all relevant processes or decisions are complete.
- 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_69c68a5376748190bb500f03df86e93e |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6e92cc8ac8190a6448b79496a8249 |
completed | March 27, 2026, 8:31 p.m. |
| PD | Predicate disambiguation | batch_69c6e757fed4819091b0a096e3befc3a |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:52 p.m.