Triple
T22684829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Documents of Jewish Sectaries |
E560882
|
entity |
| Predicate | originalTextsLanguage |
P5459
|
FINISHED |
| Object | 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: Hebrew | Statement: [Documents of Jewish Sectaries, originalTextsLanguage, Hebrew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalTextsLanguage Context triple: [Documents of Jewish Sectaries, originalTextsLanguage, Hebrew]
-
A.
originalTextLanguage
chosen
Indicates the language in which a text was originally written or created before any translation or adaptation.
-
B.
originalLanguageText
Indicates that a text is expressed in its original, untranslated language.
-
C.
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.
-
D.
originalLanguageContext
Indicates the language in which something was first created or expressed, providing the original linguistic context for its content or meaning.
-
E.
originalLanguageAuthor
Indicates that an author created a work in a particular original 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f17862c8a48190912a8ad09dfda795 |
completed | April 29, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:12 p.m.