Triple
T4415894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Monday |
E94971
|
entity |
| Predicate | associatedReading |
P37
|
FINISHED |
| Object | Gospel accounts of the last week of Jesus |
—
|
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: Gospel accounts of the last week of Jesus | Statement: [Holy Monday, associatedReading, Gospel accounts of the last week of Jesus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedReading Context triple: [Holy Monday, associatedReading, Gospel accounts of the last week of Jesus]
-
A.
alsoReadBy
Indicates that an item (such as a document, article, or book) has been read by another user or entity in addition to the primary one under consideration.
-
B.
relatedTo
chosen
Indicates a general, non-specific relationship or association exists between two entities.
-
C.
containsReading
Indicates that one entity includes or encompasses a particular reading (such as a measurement, value, or interpretation) within it.
-
D.
requiredReadingFor
Indicates that one item (such as a text or resource) must be read as a mandatory prerequisite or component for engaging with, understanding, or completing another item (such as a course, assignment, or program).
-
E.
relatedLibrary
Indicates that one library has a meaningful connection or association with another library, such as dependency, compatibility, or functional similarity.
- 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_69b34539638c8190abfea3eb29425210 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b354eabb2481908ad10d21e1379e7f |
completed | March 13, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69b34f5d0c54819085c08533bb58030a |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:29 p.m.