Triple
T29926680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Philip |
E760098
|
entity |
| Predicate | introducedToJesus |
P190674
|
FINISHED |
| Object | Nathanael |
—
|
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: Nathanael | Statement: [Saint Philip, introducedToJesus, Nathanael]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedToJesus Context triple: [Saint Philip, introducedToJesus, Nathanael]
-
A.
learnedChristianFaithFrom
Indicates that one entity acquired knowledge or understanding of the Christian faith through the teaching, influence, or example of another entity.
-
B.
ChristianBranch
Indicates that one entity is a branch, denomination, or subgroup within the broader Christian religious tradition of the other entity.
-
C.
spokeToJesusAbout
Indicates that one entity communicated verbally with Jesus regarding a particular topic or matter.
-
D.
convertedToReligion
Indicates that an entity adopted or changed to a particular religion, typically from a previous belief system or lack thereof.
-
E.
recognizesJesusWhen
Indicates that one entity identifies or acknowledges Jesus as such under certain conditions or at a particular time.
- 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_69f224631674819080c8d089674f9f4f |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fcce2cf9188190b3f65b362203a6a3 |
completed | May 7, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
| PDg | Predicate description generation | batch_69fccdd2d84481909a7ce22407def9c7 |
completed | May 7, 2026, 5:37 p.m. |
Created at: April 29, 2026, 6:16 p.m.