Triple
T238386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New World Translation of the Holy Scriptures |
E4873
|
entity |
| Predicate | hasLanguageEdition |
P4185
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [New World Translation of the Holy Scriptures, hasLanguageEdition, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageEdition Context triple: [New World Translation of the Holy Scriptures, hasLanguageEdition, English]
-
A.
hasInternationalVersion
Indicates that an entity has a corresponding version or counterpart adapted for use in multiple countries or international contexts.
-
B.
languageVariant
Indicates that one language is a variant, dialect, or localized form of another language.
-
C.
isLanguageOf
chosen
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).
-
D.
languageBranch
Indicates that one language belongs to, or is classified under, a broader linguistic branch or subgroup.
-
E.
hasLanguageGroup
Indicates that an entity belongs to, is associated with, or is categorized under a particular language group.
- 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_69a257c3d0708190b0871c4269d273e6 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25dacf60c8190a5c3ef455b9a8b20 |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b5f27208190ae13f34037fe582b |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.