Triple
T2497935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESV Thinline Bible |
E52394
|
entity |
| Predicate | readingFeature |
P40143
|
FINISHED |
| Object | Readable type size for thin format |
—
|
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: Readable type size for thin format | Statement: [ESV Thinline Bible, readingFeature, Readable type size for thin format]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: readingFeature Context triple: [ESV Thinline Bible, readingFeature, Readable type size for thin format]
-
A.
readingAid
Indicates that one entity assists or facilitates another entity’s ability to read or engage in reading activities.
-
B.
readingTechnology
Indicates a relationship where a reading activity involves or is carried out using a particular technology.
-
C.
containsReading
Indicates that one entity includes or encompasses a particular reading (such as a measurement, value, or interpretation) within it.
-
D.
readingApproach
Indicates the method, strategy, or manner in which an entity engages in reading a text.
-
E.
readingExperience
Indicates the relationship in which an entity engages with written or visual material, capturing the act, manner, or quality of that reading activity.
- 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_69ab4957b3a88190adf968ae0c1b931c |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd1ad2f8c81908853e97d75081e84 |
completed | March 7, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69abd0bba5348190bb4637d3165cb339 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd1aa13a08190a8757c017d8a2478 |
completed | March 7, 2026, 7:20 a.m. |
Created at: March 6, 2026, 9:46 p.m.