Triple
T898955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Committee of translators appointed by King James I |
E19404
|
entity |
| Predicate | translationSourceLanguage |
P2925
|
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: [Committee of translators appointed by King James I, translationSourceLanguage, Hebrew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: translationSourceLanguage Context triple: [Committee of translators appointed by King James I, translationSourceLanguage, Hebrew]
-
A.
sourceLanguageMeaning
Indicates that one entity expresses the meaning or sense of another entity in a particular source language.
-
B.
languageOfSources
chosen
Indicates that the specified language is the language in which the referenced sources or source materials are expressed.
-
C.
originalTextLanguage
Indicates the language in which a text was originally written or created before any translation or adaptation.
-
D.
translationMethod
Indicates the technique or process used to translate content from one language or form to another.
-
E.
translator
Indicates that one entity serves to convert or render content from one language or form into another for a second entity.
- 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_69a4939e889c8190ac148b3ac1a7f90b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad4162848190aa2787b2fa3e6575 |
completed | March 1, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69a4aa979d408190b17ccfde132ea628 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.