Triple
T518418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Letter to the Hebrews |
E10758
|
entity |
| Predicate | usesOldTestament |
P11800
|
FINISHED |
| Object | extensively |
—
|
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: extensively | Statement: [Letter to the Hebrews, usesOldTestament, extensively]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesOldTestament Context triple: [Letter to the Hebrews, usesOldTestament, extensively]
-
A.
oldTestamentSourceText
chosen
Indicates that something originates from, is based on, or is drawn from a text in the Old Testament.
-
B.
OldTestamentFirstPublished
Indicates that the Old Testament was first made publicly available in written or printed form at a particular time or by a particular edition.
-
C.
hasScripture
Indicates that one entity possesses, is associated with, or is defined by a particular scripture or set of scriptural texts.
-
D.
textBasisNewTestament
Indicates that a text is based on, derived from, or grounded in the New Testament.
-
E.
hasNewTestamentSourceLanguage
Indicates that something (such as a text, translation, or reference) is associated with a particular source language of the New Testament.
- 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_69a2e84a0d08819087e01863fcd9abf1 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f19ee6748190916603ef3a9e27f3 |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f0151e8c81909a82b58ac0515eba |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.