Triple
T18739388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asmat people |
E458249
|
entity |
| Predicate | missionaryContactWith |
P31002
|
FINISHED |
| Object | Roman Catholic missionaries |
—
|
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 Catholic missionaries | Statement: [Asmat people, missionaryContactWith, Roman Catholic missionaries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionaryContactWith Context triple: [Asmat people, missionaryContactWith, Roman Catholic missionaries]
-
A.
missionizationAt
Indicates the location or context in which a missionizing or religious conversion effort takes place.
-
B.
missionaryInfluenceFrom
chosen
Indicates that one entity exerts religious or missionary influence upon another entity or location.
-
C.
hasNotableMissionary
Indicates that an entity is associated with, or has, a notable missionary linked to it.
-
D.
isMissionary
Indicates that an entity serves as a missionary, engaging in religious outreach or proselytizing activities toward others.
-
E.
missionaryRegion
Indicates that an entity carries out or is associated with missionary activities within a specified geographic region.
- 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5768ca990819098102f8522ce401f |
completed | April 20, 2026, 12:42 a.m. |
| PD | Predicate disambiguation | batch_69e48d03766c8190a43f7681842f4f8d |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:51 a.m.