Triple
T13926401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleopas |
E334870
|
entity |
| Predicate | recognizesJesusWhen |
P112313
|
FINISHED |
| Object | Jesus breaks bread with him |
—
|
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: Jesus breaks bread with him | Statement: [Cleopas, recognizesJesusWhen, Jesus breaks bread with him]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizesJesusWhen Context triple: [Cleopas, recognizesJesusWhen, Jesus breaks bread with him]
-
A.
regardsJesusAs
Indicates that one entity holds a particular view, attitude, or evaluation of Jesus as another entity.
-
B.
recognizesSacrament
Indicates that one entity formally accepts or acknowledges the validity or legitimacy of a particular sacrament associated with another entity.
-
C.
hasTouchdownJesusView
Indicates that one entity (typically a location or property) has a view of the landmark known as "Touchdown Jesus."
-
D.
frequencyOfUseByJesus
Indicates how often Jesus is recorded as using, mentioning, or engaging in the referenced concept, term, or practice.
-
E.
recognizesConfession
Indicates that one entity acknowledges and accepts another entity’s admission of guilt or wrongdoing as a valid confession.
- 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_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. |
| PDg | Predicate description generation | batch_69de239524688190a0f2408c239cfcaa |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:16 p.m.