Triple
T36598835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christian |
E902868
|
entity |
| Predicate | regardsAsSonOfGod |
P185915
|
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, regardsAsSonOfGod, Jesus Christ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regardsAsSonOfGod Context triple: [Christian, regardsAsSonOfGod, Jesus Christ]
-
A.
regardsJesusAs
Indicates that one entity holds a particular view, attitude, or evaluation of Jesus as another entity.
-
B.
spiritualSonOf
Indicates a relationship where one person is regarded as the spiritual or religious protégé, disciple, or mentee of another, akin to a parent–child bond in a non-biological, faith-based context.
-
C.
incarnationOf
Indicates that one entity is a concrete embodiment, manifestation, or earthly form of another, typically more abstract or divine, entity.
-
D.
christologicalTitle
Indicates that one entity is identified as a Christological title (a theological designation related to Christ) of another entity.
-
E.
namedByGod
Indicates that an entity has been given its name directly by God.
- 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c3705b5c81908c84004543a71c07 |
completed | May 3, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:11 p.m.