Triple
T6317768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salinan people |
E141656
|
entity |
| Predicate | religionAfterMissionization |
P10604
|
FINISHED |
| Object | Roman Catholicism |
—
|
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: Roman Catholicism | Statement: [Salinan people, religionAfterMissionization, Roman Catholicism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religionAfterMissionization Context triple: [Salinan people, religionAfterMissionization, Roman Catholicism]
-
A.
missionaryInfluenceFrom
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.
laterReligion
chosen
Indicates that one religion or religious affiliation chronologically follows or replaces another for the same entity.
-
D.
promotedReligion
Indicates that an entity actively supported, advocated for, or worked to spread a particular religion.
-
E.
laterRevertedReligion
Indicates that an entity adopted a religion and then subsequently reverted or returned to a previous or different religious affiliation.
- 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_69c008d13b8c8190be47d896eb735605 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064c25530819080b29e0029175c00 |
completed | March 22, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69c060e5efc48190861b8266e5b0cc0c |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:29 p.m.