Triple
T2397796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESV Gospel Transformation Bible |
E47689
|
entity |
| Predicate | readingApproach |
P37920
|
FINISHED |
| Object | canonical |
—
|
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: canonical | Statement: [ESV Gospel Transformation Bible, readingApproach, canonical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: readingApproach Context triple: [ESV Gospel Transformation Bible, readingApproach, canonical]
-
A.
readingExperience
Indicates the relationship in which an entity engages with written or visual material, capturing the act, manner, or quality of that reading activity.
-
B.
containsReading
Indicates that one entity includes or encompasses a particular reading (such as a measurement, value, or interpretation) within it.
-
C.
readBy
Indicates that a particular text, document, or content item has been read or consumed by a specific person or agent.
-
D.
readsTo
Indicates that one entity reads or recites content aloud for the benefit of another entity.
-
E.
readingTechnology
Indicates a relationship where a reading activity involves or is carried out using a particular technology.
- 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_69a88a1c450c81909f61abb8b6863885 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc8c5f0948190b4ea729693d8c306 |
completed | March 7, 2026, 6:42 a.m. |
| PD | Predicate disambiguation | batch_69abc5a3825c81909ec6111dfc165453 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abc664317c8190a6bb5a5065c21bde |
completed | March 7, 2026, 6:32 a.m. |
Created at: March 4, 2026, 7:57 p.m.