Triple
T207602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New International Version |
E4641
|
entity |
| Predicate | digitalAvailability |
P7415
|
FINISHED |
| Object | Bible apps |
—
|
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: Bible apps | Statement: [New International Version, digitalAvailability, Bible apps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: digitalAvailability Context triple: [New International Version, digitalAvailability, Bible apps]
-
A.
availableAs
Indicates that one entity can be used, accessed, or offered in the form, role, or capacity of another entity.
-
B.
availability
chosen
Indicates that an entity is present, accessible, or ready for use or interaction by another entity.
-
C.
hasDigitalLibrary
Indicates that an entity maintains or provides access to a collection of digital resources or publications.
-
D.
hasDigitalArchive
Indicates that an entity maintains or is associated with a collection of materials stored in a digital archive.
-
E.
hasDigitalEncoding
Indicates that one entity is represented, stored, or expressed using a specific digital code or encoding scheme provided by another entity.
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25e2aba74819093eddd8d820260c0 |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b4c7f908190876c1041db52dffc |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.