Triple
T2965532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jachin |
E80151
|
entity |
| Predicate | hasScripturalStatus |
P16327
|
FINISHED |
| Object | Old Testament object |
—
|
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: Old Testament object | Statement: [Jachin, hasScripturalStatus, Old Testament object]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScripturalStatus Context triple: [Jachin, hasScripturalStatus, Old Testament object]
-
A.
scripturalStatus
chosen
Indicates the relationship between a text and its recognition or classification as scriptural, canonical, or authoritative within a religious or doctrinal tradition.
-
B.
hasScripture
Indicates that one entity possesses, is associated with, or is defined by a particular scripture or set of scriptural texts.
-
C.
hasSacredText
Indicates that an entity possesses or is associated with a particular sacred or religious text.
-
D.
doctrinalStatus
Indicates the formal standing or classification of a belief, teaching, or doctrine within a particular religious or ideological system.
-
E.
hasLanguageOfScripture
Indicates that an entity’s scriptural or sacred texts are written or expressed in a specified language.
- 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_69ad8b1341848190bd19dbf46892887d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad995a28e88190a4d6b9ef2c0d8e61 |
completed | March 8, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69ad960e71f8819088179d11248c6ed0 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:58 p.m.