Triple
T26592035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sicangu Oyate |
E667382
|
entity |
| Predicate | hasContemporaryReligions |
P158143
|
FINISHED |
| Object | Christianity |
—
|
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: Christianity | Statement: [Sicangu Oyate, hasContemporaryReligions, Christianity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContemporaryReligions Context triple: [Sicangu Oyate, hasContemporaryReligions, Christianity]
-
A.
contemporaryReligion
Indicates that two entities practice or are associated with religions that exist and are followed during the same historical time period.
-
B.
haveModernReligion
chosen
Indicates that an entity practices, follows, or is associated with a contemporary or currently existing religion.
-
C.
religionsPresent
Indicates that one or more religions are present, practiced, or represented in relation to a given entity or context.
-
D.
modernReligionMix
Indicates a relationship where elements from multiple religious traditions are combined or blended into a contemporary, syncretic religious practice or identity.
-
E.
hasReligious
Indicates that an entity is associated with, practices, or adheres to a particular religion or 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_69ee9cfc385081909ac9ae178030a06e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
Created at: April 27, 2026, 2:08 a.m.