Triple
T35902036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eudeve people |
E1038376
|
entity |
| Predicate | colonialMissionizationBy |
P31002
|
FINISHED |
| Object | Jesuits |
—
|
NE NERFINISHED |
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: Jesuits | Statement: [Eudeve people, colonialMissionizationBy, Jesuits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colonialMissionizationBy Context triple: [Eudeve people, colonialMissionizationBy, Jesuits]
-
A.
missionaryInfluenceFrom
chosen
Indicates that one entity exerts religious or missionary influence upon another entity or location.
-
B.
missionizationAt
Indicates the location or context in which a missionizing or religious conversion effort takes place.
-
C.
historicalMissionaryUse
Indicates that something was used or employed by missionaries in a historical context.
-
D.
colonialMotivation
Indicates the reasons or driving forces behind a colonial power’s decision to establish, expand, or maintain control over another territory or people.
-
E.
religionDuringColonialPeriod
Indicates that an entity’s religion is characterized specifically in the context of the colonial period.
- 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_69f76e2190f88190beb2eed798a4ef01 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa6b70948190a9f0b5f76c095d4e |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:07 p.m.