Triple
T207590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New International Version |
E4641
|
entity |
| Predicate | basedOnOriginalLanguages |
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: [New International Version, basedOnOriginalLanguages, Hebrew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnOriginalLanguages Context triple: [New International Version, basedOnOriginalLanguages, Hebrew]
-
A.
originalPublicationLanguageVariant
Indicates that one language is a specific variant or version of the language in which a work was originally published.
-
B.
hasLanguageOfOrigin
Indicates that one entity has its origin or source in the language specified by another entity.
-
C.
originalTitleLanguage
Indicates the language in which a work’s original title was written or expressed.
-
D.
originalTextLanguage
chosen
Indicates the language in which a text was originally written or created before any translation or adaptation.
-
E.
isLanguageOf
Indicates that a particular language is used as the official or primary language associated with a given entity (such as a person, document, or region).
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25e2aba74819093eddd8d820260c0 |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b4c7f908190876c1041db52dffc |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.