Triple
T1614683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Protestant Reformed Churches in America |
E34688
|
entity |
| Predicate | missionWork |
P8671
|
FINISHED |
| Object | domestic missions |
—
|
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: domestic missions | Statement: [Protestant Reformed Churches in America, missionWork, domestic missions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionWork Context triple: [Protestant Reformed Churches in America, missionWork, domestic missions]
-
A.
missionizationAt
Indicates the location or context in which a missionizing or religious conversion effort takes place.
-
B.
mission
Indicates that an entity is assigned or engaged in a specific task, operation, or purpose-directed undertaking.
-
C.
missionFocus
chosen
Indicates that an entity’s primary attention, effort, or resources are directed toward a particular mission, goal, or objective.
-
D.
missionStart
Indicates the point in time or event at which a mission or task officially begins.
-
E.
ministry
Indicates that an entity serves as a governmental ministry responsible for specific public functions or policy areas in relation to another entity.
- 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_69a885ffc5ec819091afa325d5f9611c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93fef600c819080fe75c42c8e6dac |
completed | March 5, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69a907c52a548190b648a31ea306dd5b |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.