Triple
T15477667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1 Chronicles 11 |
E376825
|
entity |
| Predicate | languageOriginallyWrittenIn |
P5459
|
FINISHED |
| Object | Biblical Hebrew |
—
|
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: Biblical Hebrew | Statement: [1 Chronicles 11, languageOriginallyWrittenIn, Biblical Hebrew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOriginallyWrittenIn Context triple: [1 Chronicles 11, languageOriginallyWrittenIn, Biblical Hebrew]
-
A.
originalLanguageOfWholeWork
Indicates that a given language is the primary or original language in which an entire work (such as a book, film, or other complete creation) was first produced or expressed.
-
B.
originalLanguageAuthor
Indicates that an author created a work in a particular original language.
-
C.
languageOfWritings
Indicates that a specified language is the one in which certain writings or written works are composed.
-
D.
languageOfOriginalDescription
Indicates that something is expressed or documented in its initial or source language version.
-
E.
originalTextLanguage
chosen
Indicates the language in which a text was originally written or created before any translation or adaptation.
- 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f88a5dc8190a2d7830748e29180 |
completed | April 16, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69ded2874b788190999158e0f043be21 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:34 a.m.