Triple
T23807197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penitential Act of the post-Vatican II Mass |
E589739
|
entity |
| Predicate | isRequiredOn |
P86606
|
FINISHED |
| Object | Sundays |
—
|
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: Sundays | Statement: [Penitential Act of the post-Vatican II Mass, isRequiredOn, Sundays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRequiredOn Context triple: [Penitential Act of the post-Vatican II Mass, isRequiredOn, Sundays]
-
A.
requiredOn
chosen
Indicates that one entity must exist, be present, or be fulfilled on a specific other entity, date, or condition as a mandatory requirement.
-
B.
requiredTo
Indicates that one entity has an obligation or necessity to perform an action or satisfy a condition in relation to another entity or context.
-
C.
isObligatory
Indicates that an entity is required or must be performed, fulfilled, or complied with according to some rule, norm, or obligation.
-
D.
requiredBy
Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
-
E.
isMandatoryFor
Indicates that something is required or compulsory for another thing to occur, be valid, or be completed.
- 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_69e25d19fecc8190a5cf39bbb18d5d7f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c752ff6481908cfc20d4f178d526 |
completed | April 29, 2026, 8:54 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:56 p.m.