Triple
T4897144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiss of Judas |
E109708
|
entity |
| Predicate | isRememberedIn |
P12313
|
FINISHED |
| Object | Christian liturgy of Holy Week |
—
|
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: Christian liturgy of Holy Week | Statement: [Kiss of Judas, isRememberedIn, Christian liturgy of Holy Week]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRememberedIn Context triple: [Kiss of Judas, isRememberedIn, Christian liturgy of Holy Week]
-
A.
rememberedFor
Indicates that one entity is known or recognized primarily because of, or in association with, another entity or achievement.
-
B.
memorizedBy
Indicates that some content, information, or material has been learned and retained in memory by a particular entity.
-
C.
recalledBy
Indicates that an entity is brought back, retrieved, or remembered as a result of another entity’s action or prompting.
-
D.
hasUserMemory
Indicates that an entity maintains or is associated with stored information about a specific user.
-
E.
recalledIn
chosen
Indicates that an entity is mentioned, remembered, or brought up again within a specific context, such as a document, conversation, or event.
- 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_69bd4410bbf88190aad50d2451c863d6 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd706245e48190a61d573438461c30 |
completed | March 20, 2026, 4:05 p.m. |
| PD | Predicate disambiguation | batch_69bd6c306b188190a08a7856beb76db4 |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:28 p.m.