Triple
T29926679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Philip |
E760098
|
entity |
| Predicate | calledToFollowJesusBy |
P154227
|
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: [Saint Philip, calledToFollowJesusBy, Jesus Christ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calledToFollowJesusBy Context triple: [Saint Philip, calledToFollowJesusBy, Jesus Christ]
-
A.
calledByJesusFrom
Indicates that one entity was personally called or summoned by Jesus from a particular source, place, or prior state.
-
B.
calledToFollowBy
chosen
Indicates that one entity has been summoned, invited, or designated by another entity to follow, accompany, or pursue a path or role associated with that other entity.
-
C.
spokeToJesusAbout
Indicates that one entity communicated verbally with Jesus regarding a particular topic or matter.
-
D.
recognizesJesusWhen
Indicates that one entity identifies or acknowledges Jesus as such under certain conditions or at a particular time.
-
E.
regardsJesusAs
Indicates that one entity holds a particular view, attitude, or evaluation of Jesus as another entity.
- 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_69f224631674819080c8d089674f9f4f |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67797fe5c81909575b762f32b63ef |
completed | May 2, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 6:16 p.m.