Triple
T4463778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheer Thursday |
E98323
|
entity |
| Predicate | commemoratesEventWith |
P55572
|
FINISHED |
| Object | disciples 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: disciples of Jesus | Statement: [Sheer Thursday, commemoratesEventWith, disciples of Jesus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commemoratesEventWith Context triple: [Sheer Thursday, commemoratesEventWith, disciples of Jesus]
-
A.
commemoratesEventOn
Indicates that one entity marks, honors, or observes a specific event on a particular date or occasion.
-
B.
commemorativeEvent
Indicates an event held specifically to honor, remember, or mark the significance of a person, group, or past occurrence.
-
C.
commemoratesEventDescribedIn
Indicates that something serves to honor or remember an event that is described in a particular source or representation.
-
D.
commemoratedBy
Indicates that something is honored, remembered, or celebrated through a particular action, event, object, or representation.
-
E.
commemoratedIn
Indicates that something is honored, remembered, or recognized within a particular work, event, place, or medium.
- F. None of above. chosen
Provenance (4 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_69b3454a7c608190944f5455c8031d73 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3567913788190ac4f28fbe63a4fa9 |
completed | March 13, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69b34f65f6448190abfadb2ae5658798 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b34ff7018c81908ad8597e525c042b |
completed | March 12, 2026, 11:44 p.m. |
Created at: March 12, 2026, 11:34 p.m.