Triple
T18917690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John 6 |
E462762
|
entity |
| Predicate | containsDiscourse |
P33880
|
FINISHED |
| Object | Bread of Life discourse |
—
|
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: Bread of Life discourse | Statement: [John 6, containsDiscourse, Bread of Life discourse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsDiscourse Context triple: [John 6, containsDiscourse, Bread of Life discourse]
-
A.
containsDiscussionOf
chosen
Indicates that one entity includes or features a discussion, treatment, or consideration of another entity as a topic or subject.
-
B.
discourse
Indicates that one entity engages in extended verbal or written communication or discussion with another entity.
-
C.
hasDiscourseParticle
Indicates that one element functions as a discourse particle in relation to another within a communicative or textual context.
-
D.
discussedAs
Indicates that one entity is talked about, treated, or examined in terms of another entity, often as an example, case, or framing concept.
-
E.
includesSubdialogue
Indicates that one dialogue segment contains another dialogue segment nested within it as a subordinate part.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c62884988190a362ada1a0a47134 |
completed | April 20, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:59 a.m.