Triple
T33736108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rose Sunday |
E864417
|
entity |
| Predicate | hasIntroit |
P97123
|
FINISHED |
| Object | "Laetare Jerusalem" |
—
|
NE NERFINISHED |
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: "Laetare Jerusalem" | Statement: [Rose Sunday, hasIntroit, "Laetare Jerusalem"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIntroit Context triple: [Rose Sunday, hasIntroit, "Laetare Jerusalem"]
-
A.
introit
chosen
Indicates the introductory section or opening part of a liturgical service, musical work, or formal ceremony.
-
B.
hasPianoIntroBy
Indicates that something (typically a musical work) features an introductory section played on piano that is performed or created by a specified agent.
-
C.
hasIntro
Indicates that an entity includes or is associated with an introductory section or opening part.
-
D.
isIntroTrack
Indicates that a track serves as the introductory piece, typically opening or setting the stage for the rest of a collection (such as an album, playlist, or set).
-
E.
introitTranslation
Indicates that one entity is a translation of an introit (a liturgical entrance chant) into the language or form represented by the other entity.
- 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_69f3498b24b8819096a65009e521d0e1 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a00037bf4148190a58593d30efdd3f8 |
completed | May 10, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_6a0000b7af608190b718fc4111bcdad8 |
completed | May 10, 2026, 3:51 a.m. |
Created at: May 1, 2026, 1:44 a.m.