Triple
T23861528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nathanael |
E592462
|
entity |
| Predicate | expressedFaithIn |
P51521
|
FINISHED |
| Object | Jesus as Son of God |
E124999
|
NE 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 as Son of God | Statement: [Nathanael, expressedFaithIn, Jesus as Son of God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expressedFaithIn Context triple: [Nathanael, expressedFaithIn, Jesus as Son of God]
-
A.
mainFaith
Indicates that one entity is the primary or predominant religious belief or faith tradition associated with another entity.
-
B.
theologicalBelief
chosen
Indicates that one entity holds or endorses a specific religious or theological doctrine, view, or set of beliefs about the divine or spiritual matters.
-
C.
religiousAttitude
Indicates an entity’s stance, disposition, or orientation toward religion or religious beliefs.
-
D.
religionOrBelief
Indicates that one entity holds, practices, or is associated with a particular religion, faith, or belief system.
-
E.
theologyExpressedIn
Indicates that a theological idea, doctrine, or perspective is articulated, represented, or communicated through a particular medium, work, or expression.
- F. None of above.
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_69e25d22eb488190914b193aff952e83 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cae0b4bc819089f491d9e817d160 |
completed | April 29, 2026, 9:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0f69ba28fc81908eff51ddfefd7cda |
completed | May 21, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:13 p.m.