Triple
T27371963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tontemboan people |
E690347
|
entity |
| Predicate | colonialMissionaryActivity |
P163095
|
FINISHED |
| Object | Protestant 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: Protestant missions | Statement: [Tontemboan people, colonialMissionaryActivity, Protestant missions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colonialMissionaryActivity Context triple: [Tontemboan people, colonialMissionaryActivity, Protestant missions]
-
A.
missionaryInfluenceFrom
Indicates that one entity exerts religious or missionary influence upon another entity or location.
-
B.
historicalMissionaryUse
Indicates that something was used or employed by missionaries in a historical context.
-
C.
missionaryActivityFrom
chosen
Indicates that a missionary activity originates from or is carried out by a specified source entity.
-
D.
missionizationAt
Indicates the location or context in which a missionizing or religious conversion effort takes place.
-
E.
missionaryOrganization
Indicates that an entity is a religious or faith-based organization dedicated to missionary work or activities.
- 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_69ef51ff826081909e42c8e2bfb97941 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 12:19 p.m.