Triple
T24998258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JAARS, North Carolina |
E625634
|
entity |
| Predicate | hasReligiousAffiliationContext |
P27867
|
FINISHED |
| Object | Christian missions support |
—
|
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: Christian missions support | Statement: [JAARS, North Carolina, hasReligiousAffiliationContext, Christian missions support]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligiousAffiliationContext Context triple: [JAARS, North Carolina, hasReligiousAffiliationContext, Christian missions support]
-
A.
hasReligious
Indicates that an entity is associated with, practices, or adheres to a particular religion or religious affiliation.
-
B.
hasAssociatedReligion
chosen
Indicates that an entity is connected with or linked to a particular religion.
-
C.
hasReligiousType
Indicates that an entity is associated with or classified under a particular religion or religious category.
-
D.
hasReligiousAffiliationInName
Indicates that an entity’s name explicitly includes or reflects a religious affiliation or association.
-
E.
hasReligiousOrganization
Indicates that an entity is associated with, governed by, or belongs to a specific religious organization.
- 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 18, 2026, 6:04 a.m.