Triple
T29350845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oahe Mission |
E744305
|
entity |
| Predicate | languageOfMissionaryWork |
P194408
|
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: [Oahe Mission, languageOfMissionaryWork, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfMissionaryWork Context triple: [Oahe Mission, languageOfMissionaryWork, English]
-
A.
languageOfReligion
Indicates the language in which a particular religion is traditionally expressed, practiced, or documented.
-
B.
hasLanguageOfMission
Indicates that an entity (such as a mission or project) is associated with a specific language used for its communication, documentation, or operation.
-
C.
hasLanguageOfScripture
Indicates that an entity’s scriptural or sacred texts are written or expressed in a specified language.
-
D.
primaryLanguageOfEvangelization
chosen
Indicates the language primarily used to communicate and spread religious teachings or evangelistic messages to a target audience.
-
E.
languageOfGospelTraditionally
Indicates the language in which a particular Gospel is traditionally believed or held to have been written or transmitted.
- 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_69f0a79a2d748190bc30abd469298b37 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fe8ddf70e48190a917eb9e8f7b6966 |
completed | May 9, 2026, 1:29 a.m. |
| PD | Predicate disambiguation | batch_69fe87ef94dc81909bb00ec8d6de9bcd |
completed | May 9, 2026, 1:03 a.m. |
Created at: April 28, 2026, 2:06 p.m.