Triple
T36598834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christian |
E902868
|
entity |
| Predicate | recognizesAsMessiah |
P112313
|
FINISHED |
| Object | Jesus Christ |
—
|
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: Jesus Christ | Statement: [Christian, recognizesAsMessiah, Jesus Christ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizesAsMessiah Context triple: [Christian, recognizesAsMessiah, Jesus Christ]
-
A.
messianicFigureAssociated
Indicates a relationship in which a person, symbol, or concept is linked or connected to a messianic figure, role, or expectation.
-
B.
regardsAsSonOfGod
Indicates that one entity considers or acknowledges another entity as the Son of God.
-
C.
recognizesJesusWhen
chosen
Indicates that one entity identifies or acknowledges Jesus as such under certain conditions or at a particular time.
-
D.
regardsJesusAs
Indicates that one entity holds a particular view, attitude, or evaluation of Jesus as another entity.
-
E.
placeInStructureOfMessiah
Indicates the position or role that something or someone occupies within the overall structure or framework associated with the Messiah.
- 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: May 3, 2026, 4:11 p.m.