Triple
T26214498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mota language |
E655582
|
entity |
| Predicate | usedInBibleTranslation |
P153342
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Mota language, usedInBibleTranslation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInBibleTranslation Context triple: [Mota language, usedInBibleTranslation, yes]
-
A.
usedScriptureTranslation
Indicates that one entity employed or relied on a particular translation of scripture in its actions, works, or communications.
-
B.
bibleTranslationIn
chosen
Indicates that a particular Bible translation is used, available, or occurs within a specified language, region, or context.
-
C.
usedToTranslate
Indicates that one entity served as the tool, method, or medium for translating another entity from one language or representation to another.
-
D.
scriptureTranslatedBy
Indicates that a particular scripture has been translated by a specific agent (such as a person, group, or organization).
-
E.
scriptureTypeTranslated
Indicates that a scripture or sacred text has been translated into a particular type, version, or format.
- 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 26, 2026, 8:53 p.m.