Triple
T2294552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESV Large Print Bible |
E51579
|
entity |
| Predicate | readingAid |
P39027
|
FINISHED |
| Object | large font size |
—
|
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: large font size | Statement: [ESV Large Print Bible, readingAid, large font size]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: readingAid Context triple: [ESV Large Print Bible, readingAid, large font size]
-
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.
readingTechnology
Indicates a relationship where a reading activity involves or is carried out using a particular technology.
-
D.
requiredReadingFor
Indicates that one item (such as a text or resource) must be read as a mandatory prerequisite or component for engaging with, understanding, or completing another item (such as a course, assignment, or program).
-
E.
readsTo
Indicates that one entity reads or recites content aloud for the benefit of another entity.
- 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_69a88b09c644819090b503456d96bf70 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abcd0e42248190ada33b84d75caa64 |
completed | March 7, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69abc589295c819092989820c2b4e9d8 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abcd0d01ac8190935fe904905cb233 |
completed | March 7, 2026, 7 a.m. |
Created at: March 4, 2026, 7:49 p.m.