Triple
T13926399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleopas |
E334870
|
entity |
| Predicate | conversationTopicWithJesus |
P60677
|
FINISHED |
| Object | events of Jesus’ crucifixion |
—
|
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: events of Jesus’ crucifixion | Statement: [Cleopas, conversationTopicWithJesus, events of Jesus’ crucifixion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conversationTopicWithJesus Context triple: [Cleopas, conversationTopicWithJesus, events of Jesus’ crucifixion]
-
A.
canDiscuss
Indicates that one entity is able or permitted to engage in a discussion or conversation with another entity.
-
B.
religiousTopicAddressed
Indicates that a subject deals with, discusses, or focuses on a religious theme, issue, or question.
-
C.
subjectReligion
Indicates that the subject is associated with, practices, or adheres to a particular religion.
-
D.
openingTopic
chosen
Indicates the primary subject or theme that initiates a discussion, conversation, or document.
-
E.
frequencyOfUseByJesus
Indicates how often Jesus is recorded as using, mentioning, or engaging in the referenced concept, term, or practice.
- 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2aa7e9248190b0523415b9224e2f |
completed | April 14, 2026, 11:53 a.m. |
| PD | Predicate disambiguation | batch_69de059e4ba881908554f72e889719fa |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:16 p.m.