Triple
T6370278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Board of Commissioners for Foreign Missions |
E143326
|
entity |
| Predicate | languageActivity |
P13195
|
FINISHED |
| Object | Bible translation |
—
|
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: Bible translation | Statement: [American Board of Commissioners for Foreign Missions, languageActivity, Bible translation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageActivity Context triple: [American Board of Commissioners for Foreign Missions, languageActivity, Bible translation]
-
A.
languageCapacity
Indicates the extent to which an entity is able to understand, produce, or otherwise use language.
-
B.
activityDomain
chosen
Indicates the general field, sector, or area of activity within which an entity operates or performs its main actions.
-
C.
activityType
Indicates the specific kind or category of action or event that an entity is engaged in or associated with.
-
D.
languageDiscussedIn
Indicates that a particular language is the topic of discussion within a specified context, source, or discourse.
-
E.
languagesSpoken
Indicates that an entity is able to communicate using one or more specified languages.
- 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_69c008d8c61081908bcaf61510d881ed |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c068277f6c81908e6a55e006f0c229 |
completed | March 22, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69c060ee055081908c79a1d151bd74cd |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:33 p.m.