Triple
T23861524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nathanael |
E592462
|
entity |
| Predicate | recognizedByJesusAs |
P310
|
FINISHED |
| Object | an Israelite in whom is no deceit |
—
|
LITERAL 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: an Israelite in whom is no deceit | Statement: [Nathanael, recognizedByJesusAs, an Israelite in whom is no deceit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedByJesusAs Context triple: [Nathanael, recognizedByJesusAs, an Israelite in whom is no deceit]
-
A.
recognizesJesusWhen
Indicates that one entity identifies or acknowledges Jesus as such under certain conditions or at a particular time.
-
B.
regardsJesusAs
Indicates that one entity holds a particular view, attitude, or evaluation of Jesus as another entity.
-
C.
namedByGod
Indicates that an entity has been given its name directly by God.
-
D.
recognizedAs
chosen
Indicates that one entity is acknowledged or accepted as having the identity, role, status, or classification of another entity.
-
E.
recognizedFor
Indicates that one entity is acknowledged, credited, or honored for a particular achievement, quality, contribution, or work associated with 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_69e25d22eb488190914b193aff952e83 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cae0b4bc819089f491d9e817d160 |
completed | April 29, 2026, 9:09 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:13 p.m.