Triple
T1015023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book of Daniel |
E21909
|
entity |
| Predicate | divisionInChristianOldTestament |
P6836
|
FINISHED |
| Object | Prophets |
—
|
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: Prophets | Statement: [Book of Daniel, divisionInChristianOldTestament, Prophets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divisionInChristianOldTestament Context triple: [Book of Daniel, divisionInChristianOldTestament, Prophets]
-
A.
oldTestamentSourceText
Indicates that something originates from, is based on, or is drawn from a text in the Old Testament.
-
B.
subsectionOfTanakh
Indicates that one text division is a recognized subsection within the larger structure of the Tanakh.
-
C.
scripturalLawCode
Indicates that one entity is a law code or set of legal prescriptions as defined or authorized by a particular scriptural or religious text for another entity.
-
D.
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.
-
E.
scriptureType
chosen
Indicates the classification or category of a scripture in relation to its type or genre.
- 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_69a493c68e24819080ed0ee8bcfd5ce0 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7c05060819083c51717874074c8 |
completed | March 1, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69a4b7238d4c8190b22d6c2ac0ac4911 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.