Triple
T26888675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | African Independent Churches |
E677111
|
entity |
| Predicate | causeOfOrigin |
P168581
|
FINISHED |
| Object | resistance to European missionary control |
—
|
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: resistance to European missionary control | Statement: [African Independent Churches, causeOfOrigin, resistance to European missionary control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfOrigin Context triple: [African Independent Churches, causeOfOrigin, resistance to European missionary control]
-
A.
speciesOrigin
Indicates the place, environment, or source from which a species originally arose or evolved.
-
B.
countryOfOrigin
Indicates the country from which an entity originally comes or was first produced, created, or established.
-
C.
placeOfOrigin
Indicates the location or source from which an entity originally comes or was created.
-
D.
describesOriginOf
Indicates that one entity specifies or explains the source, provenance, or origin of another entity.
-
E.
ingredientOrigin
Indicates that an ingredient comes from, is sourced in, or originates from a particular place or source.
- F. None of above. chosen
Provenance (4 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_69eee9bc0c90819085608c8bdc513a57 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f67595fa7c8190b6e9f7a8c700dd97 |
completed | May 2, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f674df80b08190adb7f7531083bbb1 |
completed | May 2, 2026, 10:04 p.m. |
Created at: April 27, 2026, 5:43 a.m.