Triple
T4698808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commentary on the Gospel of John |
E104214
|
entity |
| Predicate | examinesPassage |
P56883
|
FINISHED |
| Object | John 1:1 |
—
|
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: John 1:1 | Statement: [Commentary on the Gospel of John, examinesPassage, John 1:1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: examinesPassage Context triple: [Commentary on the Gospel of John, examinesPassage, John 1:1]
-
A.
soughtPassage
Indicates that one entity attempted to obtain or gain access to a particular passage, route, or way through something.
-
B.
examinesAuthor
chosen
Indicates that one entity critically studies, analyzes, or evaluates the work, ideas, or contributions of an author.
-
C.
parallelPassage
Indicates that one text segment corresponds closely in content or structure to another, such that they can be considered parallel versions or accounts of the same material.
-
D.
reasonForPassage
Indicates the underlying cause, motivation, or purpose that explains why a particular passage or movement occurred.
-
E.
containsEssay
Indicates that one entity includes or holds an essay as part of its contents.
- 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_69bd43e9b88481908582103dcadff3d9 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650ad0f88190844bfcb46b3071c2 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd621ba7448190a53ab1e2897acf71 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:17 p.m.